User equipments, base stations, and methods

ABSTRACT

A user equipment (UE) is described. The UE may comprise receiving circuitry configured to receive a downlink control information (DCI) format including an information field. The information field may indicate a combination of a channel access type, a cyclic prefix (CP) extension index and a channel access priority class (CAPC). The UE may also comprise transmitting circuitry configured to transmit a sounding reference signal (SRS) and a physical uplink shared channel (PUSCH). The SRS and the PUSCH may be based on the DCI format. There may be a gap between the SRS and the PUSCH. The gap may be longer than 16 microseconds. If the SRS is transmitted earlier than the PUSCH, the channel access type and the CP extension index corresponding to the indicated combination may apply to the SRS, a predetermined channel access type and a predetermined CP extension length may apply to the PUSCH, a predetermined CAPC may apply to the SRS, and the CAPC corresponding to the indicated combination may apply to the PUSCH.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to new signaling,procedures, user equipments (UEs), base stations and methods.

BACKGROUND ART

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibilityand/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs and one or more user equipments (UEs) in which systems and methodsfor downlink and uplink transmissions may be implemented;

FIG. 2 illustrates various components that may be utilized in a UE;

FIG. 3 illustrates various components that may be utilized in a gNB;

FIG. 4 is a block diagram illustrating one implementation of a UE inwhich systems and methods for downlink and uplink transmissions may beimplemented;

FIG. 5 is a block diagram illustrating one implementation of a gNB inwhich systems and methods for downlink and uplink transmissions may beimplemented;

FIG. 6 is a diagram illustrating one example of a resource grid;

FIG. 7 shows examples of several numerologies;

FIG. 8 shows examples of subframe structures for the numerologies thatare shown in FIG. 7 ;

FIG. 9 shows examples of subframe structures for the numerologies thatare shown in FIG. 7 ;

FIG. 10 is a block diagram illustrating one implementation of a gNB;

FIG. 11 is a block diagram illustrating one implementation of a UE;

FIG. 12 illustrates an example of control resource unit and referencesignal structure;

FIG. 13 illustrates an example of control channel and shared channelmultiplexing;

FIG. 14 illustrates PDCCH monitoring occasions for slot-basedscheduling;

FIG. 15 illustrates PDCCH monitoring occasions for non-slot-basedscheduling;

FIG. 16 shows an example of Channel Access procedure;

FIG. 17 shows an example of deferment of transmission;

FIG. 18 shows an example of channel access priority class for downlinktransmission(s);

FIG. 19 shows an example of channel access priority class for uplinktransmission(s);

FIG. 20 shows an example of Channel Access procedure;

FIG. 21 shows an example of Channel Access procedure;

FIG. 22 shows an example of Channel Access procedure;

FIG. 23 shows an example of CW size adjustment;

FIG. 24 shows an example of LBT for a transmission with a directionalbeam;

FIG. 25 shows an example of LBT for a transmission with a directionalbeam;

FIG. 26 shows an example of sub-band configuration;

FIG. 27 shows an example of an SFI configuration and an SFI signaling;

FIG. 28 shows an example of an SFI configuration and an SFI signaling;

FIG. 29 shows an example of signaling of slot format and COT structure;

FIG. 30 shows an example of signaling of slot format and COT structure;

FIG. 31 shows an example of signaling of slot format and COT structure;

FIG. 32 shows an example of signaling of slot format and COT structure;

FIG. 33 shows an example of signaling of slot format and COT structure;

FIG. 34 shows an example of a method for a UE; and

FIG. 35 shows an example of a method for gNB.

DESCRIPTION OF EMBODIMENTS

A user equipment (UE) is described. The UE may comprise receivingcircuitry configured to receive a downlink control information (DCI)format including an information field. The information field mayindicate a combination of a channel access type, a cyclic prefix (CP)extension index and a channel access priority class (CAPC). The UE mayalso comprise transmitting circuitry configured to transmit a soundingreference signal (SRS) and a physical uplink shared channel (PUSCH). TheSRS and the PUSCH may be based on the DCI format. There may be a gapbetween the SRS and the PUSCH. The gap may be longer than 16microseconds. If the SRS is transmitted earlier than the PUSCH, thechannel access type and the CP extension index corresponding to theindicated combination may apply to the SRS, a predetermined channelaccess type and a predetermined CP extension length may apply to thePUSCH, a predetermined CAPC may apply to the SRS, and the CAPCcorresponding to the indicated combination may apply to the PUSCH.

A base station is described. The base station may comprise transmittingcircuitry configured to transmit a downlink control information (DCI)format including an information field. The information field mayindicate a combination of a channel access type, a cyclic prefix (CP)extension index and a channel access priority class (CAPC). The basestation may also comprise receiving circuitry configured to receive asounding reference signal (SRS) and a physical uplink shared channel(PUSCH). The SRS and the PUSCH may be based on the DCI format. There maybe a gap between the SRS and the PUSCH. The gap may be longer than 16microseconds. If the SRS is received earlier than the PUSCH, the channelaccess type and the CP extension index corresponding to the indicatedcombination may apply to the SRS, a predetermined channel access typeand a predetermined CP extension length may apply to the PUSCH, apredetermined CAPC may apply to the SRS, and the CAPC corresponding tothe indicated combination may apply to the PUSCH.

A method for a user equipment (UE) is described. The method may comprisereceiving a downlink control information (DCI) format including aninformation field. The information field may indicate a combination of achannel access type, a cyclic prefix (CP) extension index and a channelaccess priority class (CAPC). The method may also comprise transmittinga sounding reference signal (SRS) and a physical uplink shared channel(PUSCH). The SRS and the PUSCH may be based on the DCI format. There maybe a gap between the SRS and the PUSCH. The gap may be longer than 16microseconds. If the SRS is transmitted earlier than the PUSCH, thechannel access type and the CP extension index corresponding to theindicated combination may apply to the SRS, a predetermined channelaccess type and a predetermined CP extension length may apply to thePUSCH, a predetermined CAPC may apply to the SRS, and the CAPCcorresponding to the indicated combination may apply to the PUSCH.

A method for a base station is described. The method may comprisetransmitting a downlink control information (DCI) format including aninformation field. The information field may indicate a combination of achannel access type, a cyclic prefix (CP) extension index and a channelaccess priority class (CAPC). The method may also comprise receiving asounding reference signal (SRS) and a physical uplink shared channel(PUSCH). The SRS and the PUSCH may be based on the DCI format. There maybe a gap between the SRS and the PUSCH. The gap may be longer than 16microseconds. If the SRS is received earlier than the PUSCH, the channelaccess type and the CP extension index corresponding to the indicatedcombination may apply to the SRS, a predetermined channel access typeand a predetermined CP extension length may apply to the PUSCH, apredetermined CAPC may apply to the SRS, and the CAPC corresponding tothe indicated combination may apply to the PUSCH.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15)including New Radio (NR) which is also known as The 3rd Generation NR(5G NR). However, the scope of the present disclosure should not belimited in this regard. At least some aspects of the systems and methodsdisclosed herein may be utilized in other types of wirelesscommunication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, vehicles, Internet of Things (IoT) devices, etc. In3GPP specifications, a wireless communication device is typicallyreferred to as a UE. However, as the scope of the present disclosureshould not be limited to the 3GPP standards, the terms “UE” and“wireless communication device” may be used interchangeably herein tomean the more general term “wireless communication device.” A UE mayalso be more generally referred to as a terminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB), a next Generation Node B (gNB) or some other similarterminology. As the scope of the disclosure should not be limited to3GPP standards, the terms “base station,” “Node B,” “eNB,” “HeNB,” and“gNB” may be used interchangeably herein to mean the more general term“base station.” Furthermore, the term “base station” may be used todenote an access point. An access point may be an electronic device thatprovides access to a network (e.g., Local Area Network (LAN), theInternet, etc.) for wireless communication devices. The term“communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB and gNB may also bemore generally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources may be indicated in the systeminformation transmitted on the downlink resources.

“Configured cells” are those cells of which the UE is aware and isallowed by an eNB to transmit or receive information. “Configuredcell(s)” may be serving cell(s). The UE may receive system informationand perform the required measurements on all configured cells.“Configured cell(s)” for a radio connection may include a primary celland/or no, one, or more secondary cell(s). “Activated cells” are thoseconfigured cells on which the UE is transmitting and receiving. That is,activated cells are those cells for which the UE monitors the physicaldownlink control channel (PDCCH) and in the case of a downlinktransmission, those cells for which the UE decodes a physical downlinkshared channel (PDSCH). “Deactivated cells” are those configured cellsthat the UE is not monitoring the transmission PDCCH. It should be notedthat a “cell” may be described in terms of differing dimensions. Forexample, a “cell” may have temporal, spatial (e.g., geographical) andfrequency characteristics.

The 5th generation communication systems, dubbed NR (New Radiotechnologies) by 3GPP, envision the use of time/frequency/spaceresources to allow for services, such as eMBB (enhanced MobileBroad-Band) transmission, URLLC (Ultra-Reliable and Low LatencyCommunication) transmission, and eMTC (massive Machine TypeCommunication) transmission. Also, in NR, single-beam and/or multi-beamoperations is considered for downlink and/or uplink transmissions.

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs 160 and one or more UEs 102 in which systems and methods fordownlink and uplink transmissions may be implemented. The one or moreUEs 102 communicate with one or more gNBs 160 using one or more physicalantennas 122 a-n. For example, a UE 102 transmits electromagneticsignals to the gNB 160 and receives electromagnetic signals from the gNB160 using the one or more physical antennas 122 a-n. The gNB 160communicates with the UE 102 using one or more physical antennas 180a-n.

The UE 102 and the gNB 160 may use one or more channels and/or one ormore signals 119, 121 to communicate with each other. For example, theUE 102 may transmit information or data to the gNB 160 using one or moreuplink channels 121. Examples of uplink channels 121 include a physicalshared channel (e.g., PUSCH (Physical Uplink Shared Channel)), and/or aphysical control channel (e.g., PUCCH (Physical Uplink ControlChannel)), etc. The one or more gNBs 160 may also transmit informationor data to the one or more UEs 102 using one or more downlink channels119, for instance. Examples of downlink channels 119 physical sharedchannel (e.g., PDSCH (Physical Downlink Shared Channel), and/or aphysical control channel (PDCCH (Physical Downlink Control Channel)),etc. Other kinds of channels and/or signals may be used.

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more receivers 120 may alsosense the channel which would to be used for uplink transmissions. Theone or more transmitters 158 may transmit signals to the gNB 160 usingone or more physical antennas 122 a-n. For example, the one or moretransmitters 158 may upconvert and transmit one or more modulatedsignals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may include received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) mayinclude overhead data and/or control data. For example, the secondUE-decoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include one or more of a UE scheduling module 126.

The UE scheduling module 126 may also be referred to as UE-side higherlayer processing module which performs higher layer processing. Theother units than UE scheduling module 126 in UE 102 may perform physicallayer processing.

In a radio communication system, physical channels (uplink physicalchannels and/or downlink physical channels) may be defined. The physicalchannels (uplink physical channels and/or downlink physical channels)may be used for transmitting information that is delivered from a higherlayer. For example, PCCH (Physical Control Channel) may be defined. PCCHis used to transmit control information.

In uplink, PCCH (e.g., Physical Uplink Control Channel (PUCCH)) is usedfor transmitting Uplink Control Information (UCI). The UCI may includeHybrid Automatic Repeat Request (HARQ-ACK), Channel State information(CSI), and/or Scheduling Request (SR). The HARQ-ACK is used forindicating a positive acknowledgement (ACK) or a negative acknowledgment(NACK) for downlink data (i.e., Transport block(s) carrying MediumAccess Control Control Element (MAC CE) and/or MAC Protocol Data Unit(MAC PDU) which may contain Downlink Shared Channel (DL-SCH)). The CSIis used for indicating state of downlink channel. Also, the SR is usedfor requesting resources of uplink data (i.e., Transport block(s)carrying MAC CE and/or MAC PDU which may contain Uplink Shared Channel(UL-SCH)).

The UE 102 may be configured, for DL, to receive code block group (CBG)based transmissions where retransmissions may be scheduled to carry oneor more sub-sets of all the code blocks of a transport block. The UE 102may be configured to transmit CBG based transmissions whereretransmissions may be scheduled to carry one or more sub-sets of allthe code blocks of a transport block.

In downlink, PCCH (e.g., Physical Downlink Control Channel (PDCCH)) maybe used for transmitting Downlink Control Information (DCI). Here, morethan one DCI formats may be defined for DCI transmission on the PDCCH.Namely, fields may be defined in the DCI format, and the fields aremapped to the information bits (i.e., DCI bits). For example, a DCIformat 1A that is used for scheduling of one physical shared channel(PSCH) (e.g., PDSCH, transmission of one downlink transport block) in acell is defined as the DCI format for the downlink. The DCI format(s)for PDSCH scheduling may include multiple information field, forexample, carrier indicator field, frequency domain PDSCH resourceallocation field, time domain PDSCH resource allocation field, bundlingsize field, MCS field, new data indicator field, redundancy versionfield, HARQ process number field, code block group flush indicator(CBGFI) field, code block group, transmission indicator (CBGTI) field,PUCCH power control field, PUCCH resource indicator field, antenna portfield, number of layer field, quasi-co-location (QCL) indication field,SRS triggering request field, and RNTI field. More than one pieces ofthe above information may be jointly coded, and in this instance jointlycoded information may be indicated in a single information field.

Also, for example, a DCI format 0 that is used for scheduling of onePSCH (e.g., PUSCH, transmission of one uplink transport block) in a cellis defined as the DCI format for the uplink. For example, informationassociated with PSCH (a PDSCH resource, PUSCH resource) allocation,information associated with modulation and coding scheme (MCS) for PSCH,and DCI such as Transmission Power Control (TPC) command for PUSCHand/or PUCCH are included the DCI format. Also, the DCI format mayinclude information associated with a beam index and/or an antenna port.The beam index may indicate a beam used for downlink transmissions anduplink transmissions. The antenna port may include DL antenna portand/or UL antenna port. The DCI format(s) for PUSCH scheduling mayinclude multiple information field, for example, carrier indicatorfield, frequency domain PUSCH resource allocation field, time domainPUSCH resource allocation field, MCS field, new data indicator field,redundancy version field, HARQ process number field, code block groupflush indicator (CBGFI) field, code block group transmission indicator(CBGTI) field, PUSCH power control field, SRS resource indicator (SRI)field, wideband and/or subband transmit precoding matrix indicator(TPMI) field, antenna port field, scrambling identity field, number oflayer field, CSI report triggering request field, CSI measurementrequest field, SRS triggering request field, and RNTI field. More thanone pieces of the above information may be jointly coded, and in thisinstance jointly coded information may be indicated in a singleinformation field.

Also, for example, PSCH may be defined. For example, in a case that thedownlink PSCH resource (e.g., PDSCH resource) is scheduled by using theDCI format, the UE 102 may receive the downlink data, on the scheduleddownlink PSCH resource. Also, in a case that the uplink PSCH resource(e.g., PUSCH resource) is scheduled by using the DCI format, the UE 102transmits the uplink data, on the scheduled uplink PSCH resource.Namely, the downlink PSCH is used to transmit the downlink data. And,the uplink PSCH is used to transmit the uplink data.

Furthermore, the downlink PSCH and the uplink PSCH are used to transmitinformation of higher layer (e.g., Radio Resource Control (RRC)) layer,and/or MAC layer). For example, the downlink PSCH and the uplink PSCHare used to transmit RRC message (RRC signal) and/or MAC Control Element(MAC CE). Here, the RRC message that is transmitted from the gNB 160 indownlink may be common to multiple UEs 102 within a cell (referred as acommon RRC message). Also, the RRC message that is transmitted from thegNB 160 may be dedicated to a certain UE 102 (referred as a dedicatedRRC message). The RRC message and/or the MAC CE are also referred to asa higher layer signal.

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the transmission data 146 and/or other information 142 mayinvolve error detection and/or correction coding, mapping data to space,time and/or frequency resources for transmission, multiplexing, etc. Theencoder 150 may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more physical antennas 180 a-n. Forexample, the receiver 178 may receive and downconvert signals to produceone or more received signals 174. The one or more received signals 174may be provided to a demodulator 172. The one or more receivers 178 mayalso sense the channel which would to be used for downlinktransmissions. The one or more transmitters 117 may transmit signals tothe UE 102 using one or more physical antennas 180 a-n. For example, theone or more transmitters 117 may upconvert and transmit one or moremodulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may include received payload data (e.g. UL TB), which may bestored in a data buffer 162. A second eNB-decoded signal 168 may includeoverhead data and/or control data. For example, the second eNB-decodedsignal 168 may provide data (e.g., Uplink control information such asHARQ-ACK feedback information for PDSCH) that may be used by the gNBoperations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include one or more of a gNB scheduling module 194. The gNBscheduling module 194 may also be referred to as gNB-side higher layerprocessing module which performs higher layer processing. The otherunits than gNB scheduling module 194 in gNB 160 may perform physicallayer processing.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the transmission data 105and/or other information included in the information 101 may involveerror detection and/or correction coding, mapping data to space, timeand/or frequency resources for transmission, multiplexing, etc. Theencoder 109 may provide encoded data 111 to the modulator 113. Thetransmission data 105 may include network data to be relayed to the UE102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator. 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialslot.

It should also be noted that one or more of the elements or partsthereof included in the gNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

The downlink physical layer processing of transport channels mayinclude: Transport block CRC attachment; Code block segmentation andcode block CRC attachment; Channel coding (LDPC coding); Physical-layerhybrid-ARQ processing; Rate matching; Scrambling; Modulation (QPSK,16QAM, 64QAM and 256QAM); Layer mapping; and Mapping to assignedresources and antenna ports.

FIG. 2 illustrates various components that may be utilized in a UE 202.The UE 202 described in connection with FIG. 2 may be implemented inaccordance with the UE 22 described in connection with FIG. 1 . The UE202 includes a processor 203 that controls operation of the UE 202. Theprocessor 203 may also be referred to as a central processing unit(CPU). Memory 205, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 207 a and data 209 a to theprocessor 203. A portion of the memory 205 may also include non-volatilerandom access memory (NVRAM). Instructions 207 b and data 209 b may alsoreside in the processor 203. Instructions 207 b and/or data 209 b loadedinto the processor 203 may also include instructions 207 a and/or data209 a from memory 205 that were loaded for execution or processing bythe processor 203. The instructions 207 b may be executed by theprocessor 203 to implement the methods described above.

The UE 202 may also include a housing that contains one or moretransmitters 258 and one or more receivers 220 to allow transmission andreception of data. The transmitter(s) 258 and receiver(s) 220 may becombined into one or more transceivers 218. One or more antennas 222 a-nare attached to the housing and electrically coupled to the transceiver218.

The various components of the UE 202 are coupled together by a bussystem 211, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 2 as the bus system211. The UE 202 may also include a digital signal processor (DSP) 213for use in processing signals. The UE 202 may also include acommunications interface 215 that provides user access to the functionsof the UE 202. The UE 202 illustrated in FIG. 2 is a functional blockdiagram rather than a listing of specific components.

FIG. 3 illustrates various components that may be utilized in a gNB 360.The gNB 360 described in connection with FIG. 3 may be implemented inaccordance with the gNB 160 described in connection with FIG. 1 . ThegNB 360 includes a processor 303 that controls operation of the gNB 360.The processor 303 may also be referred to as a central processing unit(CPU). Memory 305, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 307 a and data 309 a to theprocessor 303. A portion of the memory 305 may also include non-volatilerandom access memory (NVRAM). Instructions 307 b and data 309 b may alsoreside in the processor 303. Instructions 307 b and/or data 309 b loadedinto the processor 303 may also include instructions 307 a and/or data309 a from memory 305 that were loaded for execution or processing bythe processor 303. The instructions 307 b may be executed by theprocessor 303 to implement the methods described above.

The gNB 360 may also include a housing that contains one or moretransmitters 317 and one or more receivers 378 to allow transmission andreception of data. The transmitter(s) 317 and receiver(s) 378 may becombined into one or more transceivers 376. One or more antennas 380 a-nare attached to the housing and electrically coupled to the transceiver376.

The various components of the gNB 360 are coupled together by a bussystem 311, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 3 as the bus system311. The gNB 360 may also include a digital signal processor (DSP) 313for use in processing signals. The gNB 360 may also include acommunications interface 315 that provides user access to the functionsof the gNB 360. The gNB 360 illustrated in FIG. 3 is a functional blockdiagram rather than a listing of specific components.

FIG. 4 is a block diagram illustrating one implementation of a UE 402 inwhich systems and methods for downlink and uplink transmissions may beimplemented. The UE 402 includes transmit means 458, receive means 420and control means 424. The transmit means 458, receive means 420 andcontrol means 424 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 2 aboveillustrates one example of a concrete apparatus structure of FIG. 4 .Other various structures may be implemented to realize one or more ofthe functions of FIG. 1 . For example, a DSP may be realized bysoftware.

FIG. 5 is a block diagram illustrating one implementation of a gNB 560in which systems and methods for downlink and uplink transmissions maybe implemented. The gNB 560 includes transmit means 517, receive means578 and control means 582. The transmit means 517, receive means 578 andcontrol means 582 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 3 aboveillustrates one example of a concrete apparatus structure of FIG. 5 .Other various structures may be implemented to realize one or more ofthe functions of FIG. 1 . For example, a DSP may be realized bysoftware.

FIG. 6 is a diagram illustrating one example of a resource grid. Theresource grid illustrated in FIG. 6 may be applicable for both downlinkand uplink and may be utilized in some implementations of the systemsand methods disclosed herein. More detail regarding the resource grid isgiven in connection with FIG. 1 .

In FIG. 6 , physical channels and physical signals may betransmitted/received using one or several slots 683. For a givennumerology μ, N^(μ) _(RB) is bandwidth configuration of a bandwidth part(BWP) in the serving cell, expressed in multiples of N^(RB) _(sc), whereN^(RB) _(sc) is a resource block 689 size in the frequency domainexpressed as a number of subcarriers, and N^(SF,μ) _(symb) is the numberof Orthogonal Frequency Division Multiplexing (OFDM) symbols 687 in asubframe 669. In other words, For each numerology μ and for each ofdownlink and uplink, a resource grid of N^(μ) _(RB)N^(RB) _(sc)subcarriers and N^(SF,μ) _(symb) OFDM symbols may be defined. There maybe one resource grid per antenna port p, per subcarrier spacingconfiguration (SCS, also referred to as numerology) μ, and pertransmission direction (uplink or downlink). A resource block 689 mayinclude a number of resource elements (RE) 691.

Multiple OFDM numerologies (also referred to as just numerologies) aresupported as given by Table X1. Each of the numerologies may be tied toits own subcarrier spacing Δf.

TABLE X1 μ Δf = 2^(μ) · 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 260 Normal, Extended 3 120 Normal 4 240 Normal

For subcarrier spacing configuration μ, slots are numbered n^(μ)_(s)∈{0, . . . , N^(SF,μ) _(slot)−1} in increasing order within asubframe and n^(μ) _(s,f)∈{0, . . . , N^(frame,μ) _(slot)−1} inincreasing order within a frame. There are N^(slot,μ) _(symb)consecutive OFDM symbols in a slot where N^(slot,μ) _(symb) depends onthe subcarrier spacing used as given by Table X2 for normal cyclicprefix and Table X3 for extended cyclic prefix. The number ofconsecutive OFDM symbols per subframe is N^(SF,μ) _(symb)=N^(slot,μ)_(symb)·N^(SF,μ) _(slot). The start of slot n^(μ) _(s) in a subframe isaligned in time with the start of OFDM symbol n^(μ) _(s) N^(slot,μ)_(symb) in the same subframe. Not all UEs may be capable of simultaneoustransmission and reception, implying that not all OFDM symbols in adownlink slot or an uplink slot may be used.

TABLE X2 μ N^(slot, μ) _(symb) N^(frame, μ) _(slot) N^(SF, μ) _(slot) 014 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

TABLE X3 μ N^(slot, μ) _(symb) N^(frame, μ) _(slot) N^(SF, μ) _(slot) 212 40 4

For an initial BWP, N^(μ) _(RB) may be broadcast as a part of systeminformation (e.g. Master Information Block (MIB), System InformationBlock Type 1 (SIB1)). For an SCell (including a Licensed-Assisted Access(LAA) SCell), N^(μ) _(RB) is configured by a RRC message dedicated to aUE 102. For PDSCH mapping, the available RE 691 may be the RE 691 whoseindex l fulfils l≥l_(data,start) and/or l_(data,end)≥l in a subframe.

The OFDM access scheme with cyclic prefix (CP) may be employed, whichmay be also referred to as CP-OFDM. In the downlink, PDCCH, EPDCCH(Enhanced Physical Downlink Control Channel), PDSCH and the like may betransmitted. A radio frame may include a set of slots 683 (e.g., 10slots for μ=1). The RB is a unit for assigning downlink radio resources,defined by a predetermined bandwidth (RB bandwidth) and one slot.

A resource block is defined as N^(RB) _(sc)=12 consecutive subcarriersin the frequency domain and one slot (which consists of 14 symbols fornormal CP and 12 symbols for extended CP) in the time domain.

Carrier resource blocks are numbered from 0 to N^(μ) _(RB)−1 in thefrequency domain for subcarrier spacing configuration μ. The relationbetween the carrier resource block number n_(CRB) in the frequencydomain and resource elements (k, l) is given by n_(CRB)=floor(k/N^(RB)_(sc)) where k is defined relative to the resource grid. Physicalresource blocks are defined within a carrier bandwidth part (BWP) andnumbered from 0 to N^(size) _(BWP,i)−1 where i is the number of thecarrier bandwidth part. The relation between physical and absoluteresource blocks in carrier bandwidth part i is given byn_(CRB)=n_(PRB)+N^(start) _(BWP,i)−1, where N^(start) _(BWP,i) is thecarrier resource block where carrier bandwidth part starts. Virtualresource blocks are defined within a carrier bandwidth part and numberedfrom 0 to N^(size) _(BWP,i)−1 where i is the number of the carrierbandwidth part.

A carrier bandwidth part is a contiguous set of physical resourceblocks, selected from a contiguous subset of the carrier resource blocksfor a given numerology μ on a given carrier. The number of resourceblocks N^(size) _(BWP,i) in a carrier BWP may fulfil N^(min,μ)_(RB,x)<=N^(size) _(BWP,i)<=N^(max,μ) _(RB,x). A UE can be configuredwith up to four carrier bandwidth parts in the downlink with a singledownlink carrier bandwidth part being active at a given time. The UE isnot expected to receive PDSCH or PDCCH outside an active bandwidth part.A UE can be configured with up to four carrier bandwidth parts in theuplink with a single uplink carrier bandwidth part being active at agiven time. The UE shall not transmit PUSCH or PUCCH outside an activebandwidth part.

The RB may include twelve sub-carriers in frequency domain and one ormore OFDM symbols in time domain. A region defined by one sub-carrier infrequency domain and one OFDM symbol in time domain is referred to as aresource element (RE) and is uniquely identified by the index pair (k,l^(RG)) in the resource grid, where k=0, . . . , N^(μ) _(RB)N^(RB)_(sc)−1 and l^(RG)=0, . . . , N^(SF,μ) _(symb)−1 are indices in thefrequency and time domains, respectively. Moreover, RE is uniquelyidentified by the index pairk,(l) based on a certain reference point,where l are indices in the time domain. The reference point can be basedon the resource grid, i.e. component carrier (CC) basis. Alternativelythe reference point can be based on a certain band width part in thecomponent carrier. While subframes in one CC are discussed herein,subframes are defined for each CC and subframes are substantially insynchronization with each other among CCs.

In the uplink, in addition to CP-OFDM, a Single-Carrier FrequencyDivision Multiple Access (SC-FDMA) access scheme may be employed, whichis also referred to as Discrete Fourier Transform-Spreading OFDM(DFT-S-OFDM). In the uplink, PUCCH, PDSCH, Physical Random AccessChannel (PRACH) and the like may be transmitted.

For each numerology and carrier, a resource grid of N^(max,μ)_(RB,x)N^(RB) _(sc) subcarriers and N^(SF,μ) _(symb) OFDM symbols isdefined, where N^(max,μ) _(RB,x) is given by Table X4 and x is DL or ULfor downlink and uplink, respectively. There is one resource grid perantenna port p, per subcarrier spacing configuration μ, and pertransmission direction (downlink or uplink).

TABLE X4 μ N^(min, μ) _(RB, DL) N^(max, μ) _(RB, DL) N^(min, μ)_(RB, UL) N^(max, μ) _(RB, UL) 0 20 275 24 275 1 20 275 24 275 2 20 27524 275 3 20 275 24 275 4 20 138 24 138

A UE 102 may be instructed to receive or transmit using a subset of theresource grid only. The set of resource blocks a UE is referred to as acarrier bandwidth part and may be configured to receive or transmit uponare numbered from 0 to N^(μ) _(RB)−1 in the frequency domain. The UE maybe configured with one or more carrier bandwidth parts, each of whichmay have the same or different numerology.

Transmissions in multiple cells can be aggregated where up to fifteensecondary cells can be used in addition to the primary cell. A UE 102configured for operation in bandwidth parts (BWPs) of a serving cell, isconfigured by higher layers for the serving cell a set of at most fourbandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DLbandwidth by parameter DL-BWP-index and a set of at most four BWPs fortransmissions by the UE 102 (UL BWP set) in an UL bandwidth by parameterUL-BWP-index for the serving cell. For unpaired spectrum operation, a DLBWP from the set of configured DL BWPs is linked to an UL BWP from theset of configured UL BWPs, where the DL BWP and the UL BWP have a sameindex in the respective sets. For unpaired spectrum operation, a UE 102can expect that the center frequency for a DL BWP is same as the centerfrequency for a UL BWP.

The Physical Downlink Control Channel (PDCCH) can be used to schedule DLtransmissions on PDSCH and UL transmissions on PUSCH, where the DownlinkControl Information (DCI) on PDCCH includes: Downlink assignmentscontaining at least modulation and coding format, resource allocation,and HARQ information related to DL-SCH; and Uplink scheduling grantscontaining at least modulation and coding format, resource allocation,and HARQ information related to UL-SCH. In addition to scheduling, PDCCHcan be used to for: Activation and deactivation of configured PUSCHtransmission with configured grant; Activation and deactivation of PDSCHsemi-persistent transmission; Notifying one or more UEs of the slotformat; Notifying one or more UEs of the PRB(s) and OFDM symbol(s) wherethe UE may assume no transmission is intended for the UE; Transmissionof TPC commands for PUCCH and PUSCH; Transmission of one or more TPCcommands for SRS transmissions by one or more UEs; Switching a UE'sactive bandwidth part; and Initiating a random access procedure.

In the random access procedure, the UE 102 may transmit a PRACH with arandom-access preamble in a PRACH occasion selected from PRACH occasionswhich corresponds to the index of the detected SS/PBCH block candidate.The gNB 160 may receive the PRACH in the selected PRACH occasion. Themessage 2 is a procedure in which the UE 102 attempts to detect a DCIformat 1_0 with CRC (Cyclic Redundancy Check) scrambled by an RA-RNTI(Random Access-Radio Network Temporary Identifier). The UE 102 mayattempt to detect the DCI format 1_0 in a search-space-set. The message3 is a procedure for transmitting a PUSCH scheduled by a random-accessresponse (RAR) grant included in the DCI format 1_0 detected in themessage 2 procedure. The random-access response grant is indicated bythe MAC CE included in the PDSCH scheduled by the DCI format 1_0. ThePUSCH scheduled based on the random-access response grant is either amessage 3 PUSCH or a PUSCH. The message 3 PUSCH contains a contentionresolution identifier MAC CE. The contention resolution ID MAC CEincludes a contention resolution ID. Retransmission of the message 3PUSCH is scheduled by DCI format 0_0 with CRC scrambled by a TC-RNTI(Temporary Cell-Radio Network Temporary Identifier). The message 4 is aprocedure that attempts to detect a DCI format 1_0 with CRC scrambled byeither a C-RNTI (Cell-Radio Network Temporary Identifier) or a TC-RNTI.The UE 102 may receive a PDSCH scheduled based on the DCI format 1_0.The PDSCH may include a collision resolution ID.

One or more sets of PRB(s) may be configured for DL control channelmonitoring. In other words, a control resource set is, in the frequencydomain, a set of PRBs within which the UE 102 attempts to blindly decodedownlink control information (i.e., monitor downlink control information(DCI)), where the PRBs may or may not be frequency contiguous, a UE 102may have one or more control resource sets, and one DCI message may belocated within one control resource set. In the frequency-domain, a PRBis the resource unit size (which may or may not include DMRS) for acontrol channel. A DL shared channel may start at a later OFDM symbolthan the one(s) which carries the detected DL control channel.Alternatively, the DL shared channel may start at (or earlier than) anOFDM symbol than the last OFDM symbol which carries the detected DLcontrol channel. In other words, dynamic reuse of at least part ofresources in the control resource sets for data for the same or adifferent UE 102, at least in the frequency domain may be supported.

Namely, a UE 102 may have to monitor a set of PDCCH candidates in one ormore control resource sets on one or more activated serving cells orbandwidth parts (BWPs) according to corresponding search spaces wheremonitoring implies decoding each PDCCH candidate according to themonitored DCI formats. Here, the PDCCH candidates may be candidates forwhich the PDCCH may possibly be assigned and/or transmitted. A PDCCHcandidate is composed of one or more control channel elements (CCEs).The term “monitor” means that the UE 102 attempts to decode each PDCCHin the set of PDCCH candidates in accordance with all the DCI formats tobe monitored.

The set of PDCCH candidates that the UE 102 monitors may be alsoreferred to as a search space or a search space set. That is, the searchspace (or search space set) is a set of resource that may possibly beused for PDCCH transmission.

Furthermore, a common search space (CSS) and a user-equipment searchspace (USS) are set (or defined, configured). For example, the CSS maybe used for transmission of PDCCH with DCI format(s) to a plurality ofthe UEs 102. That is, the CSS may be defined by a resource common to aplurality of the UEs 102. For example, the CSS is composed of CCEshaving numbers that are predetermined between the gNB 160 and the UE102. For example, the CSS is composed of CCEs having indices 0 to 15.

Here, the CSS may be used for transmission of PDCCH with DCI format(s)to a specific UE 102. That is, the gNB 160 may transmit, in the CSS, DCIformat(s) intended for a plurality of the UEs 102 and/or DCI format(s)intended for a specific UE 102. There may be one or more types of CSS.For example, Type 0 PDCCH CSS may be defined for a DCI format scrambledby a System Information-Radio Network Temporary Identifier (SI-RNTI) ona primary cell (PCell). Type 1 PDCCH CSS may be defined for a DCI formatscrambled by a Random Access-(RA-)RNTI. Additionally and/oralternatively, Type 1 PDCCH CSS may be used for a DCI format scrambledby a Temporary Cell-(TC-)RNTI or Cell-(C-)RNTI. Type 2 PDCCH CSS may bedefined for a DCI format scrambled by a Paging-(P-)RNTI. Type 3 PDCCHCSS may be defined for a DCI format scrambled by anInterference-(INT-)RNTI, where if a UE 102 is configured by higherlayers to decode a DCI format with CRC scrambled by the INT-RNTI and ifthe UE 102 detects the DCI format with CRC scrambled by the INT-RNTI,the UE 102 may assume that no transmission to the UE 102 is present inOFDM symbols and resource blocks indicated by the DCI format.Additionally and/or alternatively, Type 3 PDCCH CSS may be used for aDCI format scrambled by the other RNTI (e.g., Transmit PowerControl-(TPC-)RNTI, Pre-emption Indication-(PI-)RNTI, Slot FormatIndicator-(SFI-)RNTI, Semi persistent scheduling-(SPS-)RNTI, Grantfree-(GF-)RNTI, Configured Scheduling-(CS-)RNTI, URLLC-(U-)RNTI),MCS-RNTI), Autonomous Uplink-(AUL-) RNTI, Downlink FeedbackInformation-(DFI-) RNTI.

A UE 102 may be indicated by System Information Block Type® (SIB0),which is also referred to as MIB, a control resource set for Type0-PDCCHcommon search space and a subcarrier spacing and a CP length for PDCCHreception. The Type0-PDCCH common search space is defined by the CCEaggregation levels and the number of candidates per CCE aggregationlevel. The UE may assume that the DMRS antenna port associated withPDCCH reception in the Type0-PDCCH common search space and the DMRSantenna port associated with Physical Broadcast channel (PBCH) receptionare quasi-collocated with respect to delay spread, Doppler spread,Doppler shift, average delay, and spatial Rx parameters. PBCH carriesMaster Information Block (MIB) which contains most important pieces ofsystem information. A PDCCH with a certain DCI format in Type0-PDCCHcommon search space schedules a reception of a PDSCH with SIB Type1(SIB1) or with other SI messages. A UE may be indicated by SIB1 controlresource set(s) for Type1-PDCCH common search space. A subcarrierspacing and a CP length for PDCCH reception with Type1-PDCCH commonsearch space are same as for PDCCH reception with Type0-PDCCH commonsearch space. The UE may assume that the DMRS antenna port associatedwith PDCCH reception in the Type1-PDCCH common search space and the DMRSantenna port associated with PBCH reception are quasi-collocated withrespect to delay spread, Doppler spread, Doppler shift, average delay,and spatial Rx parameters. A monitoring periodicity of paging occasionsfor PDCCH in Type2-PDCCH common search space may be configured to the UEby higher layer parameter. A UE may be configured by higher layersignaling whether and/or which serving cell(s) to monitor Type3-PDCCHcommon search space.

The USS may be used for transmission of PDCCH with DCI format(s) to aspecific UE 102. That is, the USS is defined by a resource dedicated toa certain UE 102. That is, the USS may be defined independently for eachUE 102. For example, the USS may be composed of CCEs having numbers thatare determined based on a RNTI assigned by the gNB 160, a slot number ina radio frame, an aggregation level, or the like.

Here, the RNTI(s) may include C-RNTI (Cell-RNTI), Temporary C-RNTI.Also, the USS (the position(s) of the USS) may be configured by the gNB160. For example, the gNB 160 may configure the USS by using the RRCmessage. That is, the base station may transmit, in the USS, DCIformat(s) intended for a specific UE 102.

Here, the RNTI assigned to the UE 102 may be used for transmission ofDCI (transmission of PDCCH). Specifically, CRC (Cyclic Redundancy Check)parity bits (also referred to simply as CRC), which are generated basedon DCI (or DCI format), are attached to DCI, and, after attachment, theCRC parity bits are scrambled by the RNTI. The UE 102 may attempt todecode DCI to which the CRC parity bits scrambled by the RNTI areattached, and detects PDCCH (i.e., DCI, DCI format). That is, the UE 102may decode PDCCH with the CRC scrambled by the RNTI.

When the control resource set spans multiple OFDM symbols, a controlchannel candidate may be mapped to multiple OFDM symbols or may bemapped to a single OFDM symbol. One DL control channel element may bemapped on REs defined by a single PRB and a single OFDM symbol. If morethan one DL control channel elements are used for a single DL controlchannel transmission, DL control channel element aggregation may beperformed.

The number of aggregated DL control channel elements is referred to asDL control channel element aggregation level. The DL control channelelement aggregation level may be 1 or 2 to the power of an integer. ThegNB 160 may inform a UE 102 of which control channel candidates aremapped to each subset of OFDM symbols in the control resource set. Ifone DL control channel is mapped to a single OFDM symbol and does notspan multiple OFDM symbols, the DL control channel element aggregationis performed within an OFDM symbol, namely multiple DL control channelelements within an OFDM symbol are aggregated. Otherwise, DL controlchannel elements in different OFDM symbols can be aggregated.

DCI formats may be classified into at least 4 types, DL regular (alsoreferred to as DCI format 1_1), UL regular (also referred to as DCIformat 0_1), DL fallback (also referred to as DCI format 1_0) and ULfallback (also referred to as DCI format 0_0) for PDSCH and PUSCHscheduling. In addition, there may be some other types for controlsignaling. Furthermore, some more types (e.g. DCI format 0_2, 0_3, 1_2and 1_3) may be defined for scheduling of one or more PUSCH(s) and oneor more PDSCH(s), which may be applicable to an NR-based unlicensedaccess (NR-U) cell. Table X5 shows an example of a set of the DCI formattypes.

TABLE X6 DCI format Usage RNTI 0_0 Scheduling of PUSCH C-RNTI, CS-RNTI,containing up to one TB in MCS-RNTI, TC-RNTI one cell 0_1 Scheduling ofPUSCH C-RNTI, CS-RNTI, containing up to two TBs in SP-CSI-RNTI, one cellMCS-RNTI 0_2 Scheduling of one or more C-RNTI, CS-RNTI, PUSCH(s) eachcontaining MCS-RNTI, AUL-RNTI, up to one TB in one cell DFI-RNTI 0_3Scheduling of one or more C-RNTI, CS-RNTI, PUSCH(s) each containingMCS-RNTI, AUL-RNTI, up to two TBs in one cell DFI-RNTI 1_0 Scheduling ofPDSCH C-RNTI, CS-RNTI, containing up to one TB in MCS-RNTI, P-RNTI, onecell SI-RNTI, RA-RNTI, TC-RNTI 1_1 Scheduling of PDSCH C-RNTI, CS-RNTI,containing up to two TBs in MCS-RNTI one cell 1_2 Scheduling of one ormore C-RNTI, CS-RNTI, PDSCH(s) each containing MCS-RNTI up to one TB inone cell 1_3 Scheduling of one or more C-RNTI, CS-RNTI, PDSCH(s) eachcontaining MCS-RNTI up to two TBs in one cell 2_0 Notifying a group ofUEs of SFI-RNTI the slot format Notifying a group of UEs of the channeloccupancy time information related to the NR-U cell 2_1 Notifying agroup of UEs of INT-RNTI the PRB(s) and OFDM symbol(s) where UE mayassume no transmission is intended for the UE 2_2 Transmission of TPCTPC-PUSCH-RNTI, commands for PUCCH and TPC-PUCCH-RNTI PUSCH 2_3Transmission of a group of TPC-SRS-RNTI TPC commands for SRStransmissions by one or more UEs 2_4 Notifying a group of UEs of CC-RNT1common control information related to the NR-U cell

The DL regular DCI format and the UL regular DCI format may have a sameDCI payload size. The DL fallback DCI format and the UL fallback DCIformat may have a same DCI payload size. Table X6, X7, X8, and X9 showexamples of DCI formats 0_0, 0_1, 1_0 and 1_1, respectively. “Mandatory”may mean the information field is always present irrespective of RRC(re)configuration. “Optional” may mean the information field may or maynot be present depending on RRC (re)configuration. In the DL fallbackDCI format and the UL fallback DCI format, all information fields aremandatory so that their DCI payload sizes are fixed irrespective of RRC(re)configuration.

TABLE X6 Information The number Mandatory/ field of bits OptionalRemarks Identifier for 1 Mandatory The value of this bit field may bealways set DCI formats to 0, indicating an UL DCI format Frequency 15Mandatory Virtual Resource Blocks (VRBs) indicated domain using type 1resource allocation resource assignment Time domain 2 Mandatory Index ofan entry of a table providing sets of resource OFDM symbols and a slotused for PUSCH assignment transmission Frequency 1 Mandatory Flag tocontrol whether to use frequency hopping flag hopping Modulation 5Mandatory Modulation and coding scheme (MCS) for a and coding single TBwhich is contained in the PUSCH scheme New data 1 Mandatory Indicatingwhether the TB transmission is an indicator initial transmission (inwhich case the NDI value is toggled) or re-transmission (in which casethe NDI value is nottoggled). Redundancy 2 Mandatory Indicatingrate-matching pattern version HARQ 4 Mandatory process number TPC 2Mandatory command for scheduled PUSCH Padding bits, if required UL/SUL 0or 1 Optional 1 bit for UEs configured with SUL in the indicator cell asdefined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1_0before padding is larger than the number of bits for DCI format 0_0before padding; 0 bit otherwise.

TABLE X7 Information The number Mandatory/ field of bits OptionalRemarks Identifier for 1 Mandatory The value of this bit field may bealways set DCI formats to 0, indicating an UL DCI format Carrier 0 or 3Optional Indicating SCellIndex of the serving cell in indicator whichthe scheduled PUSCH is to be transmitted UL/SUL 0 or 1 Optional 0 bitfor UEs not configured with SUL in the indicator cell or UEs configuredwith SUL in the cell but only PUCCH carrier in the cell is configuredfor PUSCH transmission; 1 bit for UEs configured with SUL in the cellBandwidth 0, 1 or Optional Indicating BWP ID of the BWP which partindicator 2 contains scheduled PUSCH. If a UE does not support activeBWP change via DCI, the UE may ignore this bit field Frequency 25 Mandatory Virtual Resource Blocks (VRBs) indicated domain using type 0or type 1 resource allocation resource assignment Time domain 0, 1, 2,Mandatory Index of an entry of an RRC-configured table resource 3 or 4providing the set of OFDM symbols used for assignment PUSCH transmissionFrequency 0 or 1 Optional 0 bit if only resource allocation type 0 ishopping flag configured or if the higher layer parameterfrequencyHopping is not configured, 1 bit otherwise Modulation 5Mandatory MCS for TB(s) which are contained in the and coding PUSCHscheme New data 1 Mandatory indicator Redundancy 2 Mandatory versionHARQ 4 Mandatory process number 1st downlink 1 or 2 Mandatory 1 bit forsemi-static HARQ-ACK codebook, assignment 2 bits for dynamic HARQ-ACKcodebook. index 2nd downlink 0 or 2 Optional 2 bits for dynamic HARQ-ACKcodebook assignment with two HARQ-ACK sub-codebooks, 0 bit indexotherwise TPC 2 Mandatory command for scheduled PUSCH SRS resource 0, 1or Optional indicator 2 Precoding 0, 1, 2, Optional 0 bit if the higherlayer parameter txConfig = information 3, 4, 5 nonCodeBook or for 1antenna port and number or 6 of layers Antenna 2, 3, 4 Mandatory portsor 5 SRS request 2 or 3 Mandatory This bit field may also indicate theassociated CSI RS. CSI request 0, 1, 2, Optional The bit size may bedetermined by higher 3, 4, 5 layer parameter reportTriggerSize or 6PTRS-DMRS 0 or 2 Optional 0 bit if PTRS-UplinkConfig is not configuredassociation and transformPrecoder = disabled, or if transformPrecoder =enabled, or if maxRank = 1, 2 bits otherwise. beta_offset 0 or 2Optional 0 bit if the higher layer parameter betaOffsets = indicatorsemiStatic; otherwise 2 bits DMRS 0 or 1 Optional sequenceinitialization UL-SCH 1 Mandatory A value of “1” may indicate UL-SCHshall indicator be transmitted on the PUSCH and a value of “0” mayindicate UL-SCH shall not be transmitted on the PUSCH.

TABLE X8 Information The number Mandatory/ field of bits OptionalRemarks Identifier for DCI formats 1 Mandatory The value of this bitfield is always set to 1, indicating a DL DCI format Frequency domainresource 15 Mandatory VRBs indicated using type 1 assignment RA. Timedomain resource 4 Mandatory Index of an entry of a table assignmentproviding sets of OFDM symbols and a slot used for PDSCH transmissionVRB-to-PRB mapping 1 Mandatory Flag to control VRB-to-PRB mappingModulation and coding 5 Mandatory MCS for a single TB which is schemecontained in the PDSCH New data indicator 1 Mandatory Indicating whetherthe TB transmission is an initial transmission (in which case the NDIvalue is toggled) or re-transmission (in which case the NDI value is nottoggled). Redundancy version 2 Mandatory Indicating rate-matchingpattern HARQ process number 3 Mandatory Downlink assignment index 2Mandatory as counter DAI TPC command for 2 Mandatory TPC command for thescheduled PUCCH PUCCH on which HARQ-ACK feedback for the scheduled PDSCHis to be transmitted. PUCCH resource indicator 3 Mandatory Indicating aPUCCH resource index. PDSCH-to-HARQ_feedback 3 Mandatory Indicating atiming offset timing indicator between the slot where the scheduledPDSCH is transmitted and the slot where the corresponding PUCCH is to betransmitted.

TABLE X9 Information The number Mandatory/ field of bits OptionalRemarks Identifier for DCI 1 Mandatory The value of this bit field isalways formats set to 1, indicating a DL DCI format Carrier indicator 0or 3 Optional Indicating SCellIndex of the serving cell in which thescheduled PDSCH is transmitted Bandwidth part indicator 0, 1 or OptionalIndicating BWP ID of the BWP 2 which contains scheduled PDSCH. If a UEdoes not support active BWP change via DCI, the UE may ignore this bitfield Frequency domain 25 Mandatory VRBs, indicated using type 0 orresource assignment type 1 resource allocation Time domain resource 0,1, Optional Index of an entry of an assignment 2, 3 or RRC-configuredtable providing the 4 set of OFDM symbols used for PUSCH transmissionVRB-to-PRB mapping 0 or 1 Mandatory Flag to control VRB-to-PRB mapping 0bit if only resource allocation type 0 is configured; 1 bit otherwisePRB bundling size 0 or 1 Optional 1 bit if the higher layer parameterindicator prb-BundlingType is set to ‘dynamic’, 0 bit otherwise Ratematching indicator 0, 1 or Optional RB-level and/or RE-level indication2 of REs which are not available for the scheduled PDSCH transmission.Each bit corresponds to respective higher layer parameterrateMatchPattern. ZP CSI-RS trigger 0, 1 or Optional Indicating CSI-RSREs which are 2 not available for the scheduled PDSCH transmission. UCIon PUSCH 2 Optional Indication of beta value for UCI on informationPUSCH, possibly also other UCI-on-PUSCH-related information Modulationand coding 5 Mandatory MCS for TB1 which is contained by scheme for TB1the scheduled PDSCH. New data indicator for 1 Mandatory NDI for TB1which is contained by TB1 the scheduled PDSCH. Redundancy version for 2Mandatory RV for TB1 which is contained by TB1 the scheduled PDSCH.Modulation and coding 5 Optional MCS for TB2 which is contained byscheme for TB2 the scheduled PDSCH. Only present ifmaxNrofCodeWordsScheduledByDCI equals 2 New data indicator for 1Optional NDI for TB2 which is contained by TB2 the scheduled PDSCH. Onlypresent if maxNrofCodeWordsScheduledByDCI equals 2 Redundancy versionfor 2 Optional RV for TB2 which is contained by TB2 the scheduled PDSCH.Only present if maxNrofCodeWordsScheduledByDCI equals 2 HARQ processnumber 4 Mandatory Downlink assignment 0, 2 or Optional 4 bits if morethan one serving cell index 4 are configured in the DL and the higherlayer parameter pdsch-HARQ-ACK-Codebook = dynamic, where the 2 MSB (mostsignificant bit) bits are the counter DAI and the 2 LSB (leastsignificant bit) bits are the total DAI, 2 bits if only one serving cellis configured in the DL and the higher layer parameterpdsch-HARQ-ACK-Codebook = dynamic, where the 2 bits are the counter DAI,0 bit otherwise TPC command for 2 Mandatory TPC command for the PUCCH onscheduled PUCCH which HARQ-ACK feedback for the scheduled PDSCH is to betransmitted. PUCCH resource 3 Mandatory Indicating a PUCCH resourceindex. indicator PDSCH-to-HARQ_feedback 0, 1, 2 Optional Indicating atiming offset between timing indicator or 3 the slot where the scheduledPDSCH is transmitted and the slot where the corresponding PUCCH is to betransmitted. Antenna port(s) 4, 5 or Mandatory Indicating antenna portsused for the 6 scheduled PDSCH transmission and/or the number of CDMgroups without data (i.e. the number of CDM groups whose REs are notavailable for the PDSCH transmissions) Transmission 0 or 3 Optional 0bit if higher layer parameter configuration indication tci-PresentInDCIis not enabled, 3 bits otherwise SRS request 2 or 3 Mandatory This bitfield may also indicate the associated CSI-RS. CBG transmission 0, 2,Optional The bit size may be determined by information (CBGTI) 4, 6 orthe higher layer parameters 8 maxCodeBlockGroupsPerTransportBlock andNumber-MCS-HARQ-DL-DCI for the PDSCH. CBG flushing out 0 or 1 OptionalThe bit size may be determined by information (CBGFI) higher layerparameter codeBlockGroupFlushIndicator. DMRS sequence 0 or 1 Optionalinitialization

FIG. 7 shows examples of several numerologies. The numerology #1 (μ=0)may be a basic numerology. For example, a RE of the basic numerology isdefined with subcarrier spacing of 15 kHz in frequency domain and2048κTs+CP length (e.g., 512κTs, 160κTs or 144κTs) in time domain, whereTs denotes a baseband sampling time unit defined as 1/(15000*2048)seconds. For the μ-th numerology, the subcarrier spacing may be equal to15*2^(μ) and the effective OFDM symbol length NuTs=2048*2⁻κ^(μ)Ts. Itmay cause the symbol length is 2048*2⁻κ^(μ)Ts+CP length (e.g.,512*2⁻κ^(μ)Ts, 160*2⁻κ^(μ)Ts or 144*2⁻κ^(μ)Ts). Note that κ=64,Ts=1/(Δf_(max)·N_(f)), Δf_(max)=480·10³ Hz (i.e. Δf for μ=5), andN_(f)=4096. In other words, the subcarrier spacing of the μ+1-thnumerology is a double of the one for the μ-th numerology, and thesymbol length of the μ+1-th numerology is a half of the one for the μ-thnumerology. FIG. 7 shows four numerologies, but the system may supportanother number of numerologies.

FIG. 8 shows a set of examples of subframe structures for thenumerologies that are shown in FIG. 7 . These examples are based on theslot configuration set to 0. A slot includes 14 symbols, the slot lengthof the μ+1-th numerology is a half of the one for the μ-th numerology,and eventually the number of slots in a subframe (i.e., 1 ms) becomesdouble. It may be noted that a radio frame may include 10 subframes, andthe radio frame length may be equal to 10 ms.

FIG. 9 shows another set of examples of subframe structures for thenumerologies that are shown in FIG. 7 . These examples are based on theslot configuration set to 1. A slot includes 7 symbols, the slot lengthof the +1-th numerology is a half of the one for the μ-th numerology,and eventually the number of slots in a subframe (i.e., 1 ms) becomesdouble.

A downlink physical channel may correspond to a set of resource elementscarrying information originating from higher layers. The downlinkphysical channels may include Physical Downlink Shared Channel (PDSCH),Physical Broadcast Channel (PBCH), Physical Downlink Control Channel(PDCCH). A downlink physical signal corresponds to a set of resourceelements used by the physical layer but might not carry informationoriginating from higher layers. The downlink physical signals mayinclude Demodulation reference signals (DM-RS), Phase-tracking referencesignals (PT-RS), Channel-state information reference signal (CSI-RS)Primary synchronization signal (PSS), Secondary synchronization signal(SSS).

An uplink physical channel may correspond to a set of resource elementscarrying information originating from higher layers. The uplink physicalchannels may include Physical Uplink Shared Channel (PUSCH), PhysicalUplink Control Channel (PUCCH), Physical Random Access Channel (PRACH).An uplink physical signal is used by the physical layer but might notcarry information originating from higher layers. The uplink physicalsignals may include Demodulation reference signals (DM-RS),Phase-tracking reference signals (PT-RS), Sounding reference signal(SRS).

The Synchronization Signal and PBCH block (SSB) may consist of primaryand secondary synchronization signals (PSS, SSS), each occupying 1symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and240 subcarriers, but on one symbol leaving an unused part in the middlefor SSS. For a regular NR operation, PSS and SSS may be located indifferent OFDM symbols in between one OFDM symbol gap, with PSS first,then SSS. The periodicity of the SSB can be configured by the networkand the time locations where SSB can be sent are determined bysub-carrier spacing. Within the frequency span of a carrier, multipleSSBs can be transmitted. The physical cell identities (PCIs) of thoseSSBs may not have to be unique, i.e. different SSBs can have differentPCIs. However, when an SSB is associated with an SIB1 (also known asremaining minimum system information (RMSI)), the SSB may correspond toan individual cell, which has a unique NR Cell Global Identifier (NCGI).Such an SSB may be referred to as a Cell-Defining SSB (CD-SSB). A PCellmay be always associated to a CD-SSB located on the synchronizationraster.

Slot format indicator (SFI) may be defined to specify a format for oneor more slot(s). With SFI, the UE 102 may be able to derive at leastwhich symbols in a given slot that are ‘DL’, ‘UL’, and ‘unknown’,respectively. In addition, it may also indicate which symbols in a givenslot that are ‘reserved’. With SFI, the UE 102 may also be able toderive the number of slots for which the SFI indicates their formats.SFI may be configured by dedicated RRC configuration message.Alternatively and/or additionally, SFI may be signaled by a group-commonPDCCH (e.g., PDCCH with SFI-RNTI). Yet alternatively and/oradditionally, SFI may be broadcasted via master information block (MIB)or remaining minimum system information (RMSI).

For example, each SFI can express up to 8 combinations of ‘DL’, ‘UL’,‘Unknown’ and ‘reserved’, each combination includes N^(slot,μ) _(symb)pieces of symbol types. More specifically, given that N^(slot,μ)_(symb)=14, one combination may be ‘Unknown’ ‘Unknown’ ‘Unknown’‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’. Another combination may be all‘DL, that is ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’‘DL’ ‘DL’. Yet another combination may be all ‘UL, that is ‘UL’ ‘UL’‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’. Yet anothercombination may be a combination of ‘DL’, ‘UL’ and ‘Reserved’ such as‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘Reserved’ ‘Reserved’ ‘Reserved’‘Reserved’ ‘UL’.

‘DL’ symbols may be available for DL receptions and CSI/RRM measurementsat the UE 102 side. ‘UL’ symbols may be available for UL transmissionsat the UE 102 side. ‘Unknown’ resource may also be referred to as‘Flexible’ and can be overridden by at least by DCI indication.‘Unknown’ may be used to achieve the same as ‘Reserved’ if notoverridden by DCI and/or SFI indication. On ‘Unknown’ symbols, UE 102may be allowed to assume any DL and UL transmissions which areconfigured by higher-layer, unless overridden by DCI indicating theother direction, and any DL and UL transmissions indicated by DCI. Forexample, periodic CSI-RS, periodic CSI-IM, semi-persistently scheduledCSI-RS, periodic CSI reporting, semi-persistently scheduled CSIreporting, periodic SRS transmission, higher-layer configured Primarysynchronization signal (PSS)/secondary SS (SSS)/PBCH can be assumed(i.e. for DL, assumed to be present and to be able to perform thereception, and for UL, assumed to be able to perform the transmission).

The overriding of ‘Unknown’ symbols by the DCI means that UE 102 mayhave to assume only DL and UL transmissions (PDSCH transmission, PUSCHtransmission, aperiodic CSI-RS transmission, aperiodic CSI-IM resource,aperiodic SRS transmission) which are indicated by DCI indications. Theoverriding of ‘Unknown’ symbols by the SFI means that UE 102 may have toassume the symbols as either ‘DL’, ‘UL’, or ‘Reserved’ according to SFIindications. If the UE 102 assumes aperiodic CSI-RS transmission and/oraperiodic CSI-IM resource, the UE 102 may perform CSI and/or RRMmeasurement based on the aperiodic CSI-RS transmission and/or aperiodicCSI-IM resource. If the UE 102 does not assume aperiodic CSI-RStransmission and/or aperiodic CSI-IM resource, the UE 102 may not usethe aperiodic CSI-RS transmission and/or aperiodic CSI-IM resource forCSI and/or RRM measurement.

The UE 102 may have to monitor PDCCH on some ‘DL’ or ‘Unknown’ symbols.There may be several options to monitor PDCCH. If all of the OFDMsymbols which are assigned for a given control resource set (CORESET)are ‘DL’, the UE 102 may assume all of the OFDM symbols are valid formonitoring of a PDCCH associated with the given CORESET. In this case,the UE 102 may assume each PDCCH candidate in the CORESET is mapped toall of the OFDM symbols for time-first RE group (REG)-to-control channelelement (CCE) mapping. If all of the OFDM symbols which are assigned fora given CORESET are ‘Unknown’, the UE 102 may assume all of the OFDMsymbols are valid for monitoring of a PDCCH associated with the givenCORESET. In this case, the UE 102 may assume each PDCCH candidate in theCORESET is mapped to all of the OFDM symbols for time-first REG-to-CCEmapping.

If every OFDM symbols which is assigned for a given combination ofCORESET and search space set is either ‘UL’ or ‘Reserved’, the UE 102may assume those OFDM symbols are not valid for monitoring of a PDCCHassociated with the given combination of CORESET and search space set.If some of the OFDM symbols which are assigned for a given combinationof CORESET and search space set are ‘DL’ and the others are ‘UL’ or‘Reserved’ or if some of the OFDM symbols which are assigned for a givencombination of CORESET and search space set are ‘Unknown’ and theothers' are ‘UL’ or ‘Reserved’, the UE 102 may not monitor PDCCH in theCORESET.

NR-U may not support RMSI and/or dedicated RRC configuration of slotformat. In this case, all symbols are considered to be Flexible asdefault.

FIG. 10 is a block diagram illustrating one implementation of a gNB 1060(an example of the gNB 160). The gNB 1060 may include a higher layerprocessor 1001 (also referred to as higher layer processing circuitry),a DL transmitter 1002, a UL receiver 1003, and antennas 1004. The DLtransmitter 1002 may include a PDCCH transmitter 1005 and a PDSCHtransmitter 1006. The UL receiver 1003 may include a PUCCH receiver 1007and a PUSCH receiver 1008. The higher layer processor 1001 may managephysical layer's behaviors (the DL transmitter's and the UL receiver'sbehaviors, LBT, etc) and provide higher layer parameters to the physicallayer. The higher layer processor 1001 may obtain transport blocks fromthe physical layer. The higher layer processor 1001 may send/acquirehigher layer messages such as a common and dedicated RRC messages and/orMAC messages to/from a UE's higher layer. The higher layer processor1001 may also set and/or store higher layer parameters carried by thehigher layer messages. The higher layer processor 1001 may provide thePDSCH transmitter 1006 transport blocks and provide the PDCCHtransmitter 1005 transmission parameters related to the transportblocks. The UL receiver 1003 may receive multiplexed uplink physicalchannels and uplink physical signals via receiving antennas andde-multiplex them. The PUCCH receiver 1007 may provide the higher layerprocessor UCI. The PUSCH receiver 1008 may provide the higher layerprocessor 1001 received transport blocks. The UL receiver 1003 may alsosense a downlink channel where the DL transmitter 1002 would performdownlink transmissions.

FIG. 11 is a block diagram illustrating one implementation of a UE 1102(an example of the UE 102). The UE 1102 may include a higher layerprocessor 1111, a UL transmitter 1113, a DL receiver 1112, and antennas1114. The UL transmitter 1113 may include a PUCCH transmitter 1117 and aPUSCH transmitter 1118. The DL receiver 1112 may include a PDCCHreceiver 1115 and a PDSCH receiver 1116. The higher layer processor 1111may manage physical layer's behaviors (the UL transmitter's and the DLreceiver's behaviors, LBT, etc) and provide higher layer parameters tothe physical layer. The higher layer processor 1111 may obtain transportblocks from the physical layer. The higher layer processor 1111 maysend/acquire higher layer messages such as a common and dedicated RRCmessages and/or MAC messages to/from a UE's higher layer. The higherlayer processor 1111 may also set and/or store higher layer parameterscarried by the higher layer messages. The higher layer processor 1111may provide the PUSCH transmitter transport blocks and provide the PUCCHtransmitter 1117 UCI. The DL receiver 1112 may receive multiplexeddownlink physical channels and downlink physical signals via receivingantennas and de-multiplex them. The PDCCH receiver 1115 may provide thehigher layer processor DCI. The PDSCH receiver 1116 may provide thehigher layer processor 1111 received transport blocks. The DL receiver1112 may also sense an uplink channel where the UL transmitter 1113would perform uplink transmissions.

For downlink data transmission, the UE 1102 may attempt blind decodingof one or more PDCCH (also referred to just as control channel)candidates. This procedure is also referred to as monitoring of PDCCH.The PDCCH may carry DCI format which schedules PDSCH (also referred tojust as shared channel or data channel). The gNB 1060 may transmit PDCCHand the corresponding PDSCH in a downlink slot. Upon the detection ofthe PDCCH in a downlink slot, the UE 1102 may receive the correspondingPDSCH in the downlink slot. Otherwise, the UE 1102 may not perform PDSCHreception in the downlink slot.

FIG. 12 illustrates an example of control resource unit and referencesignal structure. A control resource set may be defined, in frequencydomain, as a set of physical resource block(s) (PRBs). For example, acontrol resource set may include PRB #i to PRB #i+3 in frequency domain.The control resource set may also be defined, in time domain, as a setof OFDM symbol(s). It may also be referred to as a duration of thecontrol resource set or just control resource set duration. For example,a control resource set may include three OFDM symbols, OFDM symbol #0 toOFDM symbol #2, in time domain. The UE 102 may monitor PDCCH in one ormore control resource sets. The PRB set may be configured with respectto each control resource set through dedicated RRC signaling (e.g., viadedicated RRC reconfiguration). The control resource set duration mayalso be configured with respect to each control resource set throughdedicated RRC signaling.

In the control resource unit and reference signal structure shown inFIG. 12 , control resource units are defined as a set of resourceelements (REs). Each control resource unit includes all REs (i.e., 12REs) within a single OFDM symbol and within a single PRB (i.e.,consecutive 12 subcarriers). REs on which reference signals (RSs) aremapped may be counted as those REs, but the REs for RSs are notavailable for PDCCH transmission and the PDCCH are not mapped on the REsfor RSs.

Multiple control resource units may be used for a transmission of asingle PDCCH. In other words, one PDCCH may be mapped the REs which areincluded in multiple control resource units. FIG. 12 shows the examplethat the UE 102 performing blind decoding of PDCCH candidates assumingthat multiple control resource units located in the same frequencycarries one PDCCH. The RSs for the PDCCH demodulation may be containedin all of the resource units on which the PDCCH is mapped. The REs forthe RS may not be available for either the PDCCH transmission or thecorresponding PDSCH transmission.

FIG. 13 illustrates an example of control channel and shared channelmultiplexing. The starting and/or ending position(s) of PDSCH may beindicated via the scheduling PDCCH. More specifically, the DCI formatwhich schedule PDSCH may include information field(s) for indicating thestarting and/or ending position(s) of the scheduled PDSCH.

The UE 102 may include a higher layer processor which is configured toacquire a common and/or dedicated higher layer message. The commonand/or dedicated higher layer message may include system informationand/or information for higher layer configuration/reconfiguration. Basedon the system information and/or higher layer configuration, the UE 102performs physical layer reception and/or transmission procedures. The UE102 may also include PDCCH receiving circuitry which is configured tomonitor a PDCCH. The PDCCH may carry a DCI format which schedule aPDSCH. Additionally and/or alternatively the PDCCH may carry a DCIformat which schedule a PUSCH. The UE 102 may also include PDSCHreceiving circuitry which is configured to receive the PDSCH upon thedetection of the corresponding PDCCH. The UE 102 may also include PUCCHtransmitting circuitry which is configured to transmit the PUCCHcarrying HARQ-ACK feedback related to the PDSCH. Additionally and/oralternatively the UE 102 may also include PUSCH transmitting circuitrywhich is configured to transmit the PUSCH upon the detection of thecorresponding PDCCH.

The gNB 160 may include a higher layer processor which is configured tosend a common and/or dedicated higher layer message. The common and/ordedicated higher layer message may include system information and/orinformation for higher layer configuration/reconfiguration. Based on thesystem information and/or higher layer configuration, the gNB 160performs physical layer reception and/or transmission procedures. ThegNB 160 may also include PDCCH transmitting circuitry which isconfigured to transmit a PDCCH. The PDCCH may carry DCI format whichschedule a PDSCH. Additionally and/or alternatively, the PDCCH may carryDCI format which schedule a PUSCH. The gNB 160 may also include PDSCHtransmitting circuitry which is configured to transmit the PDSCH uponthe transmission of the corresponding PDCCH. The gNB 160 may alsoinclude PUCCH receiving circuitry which is configured to receive thePUCCH carrying HARQ-ACK feedback related to the PDSCH. Additionallyand/or alternatively the gNB 160 may also include PUSCH receivingcircuitry which is configured to receive the PUSCH upon the detection ofthe corresponding PDCCH.

UE 102 may monitor PDCCH candidates in a control resource set. The setof PDCCH candidates may be also referred to as search space. The controlresource set may be defined by a PRB set in frequency domain and aduration in units of OFDM symbol in time domain.

For each serving cell, higher layer signaling such as common RRCmessages or UE dedicated RRC messages may configure the UE 102 with oneor more PRB set(s) for PDCCH monitoring. For each serving cell, higherlayer signaling such as common RRC messages or UE dedicated RRC messagesmay also configure the UE 102 with the control resource set duration forPDCCH monitoring.

For each serving cell, higher layer signaling configures a UE with Pcontrol resource sets. For control resource set p, 0<=p<P, theconfiguration includes: a first symbol index provided by higher layerparameter CORESET-start-symb; the number of consecutive symbols providedby higher layer parameter CORESET-time-duration; a set of resourceblocks provided by higher layer parameter CORESET-freq-dom; a CCE-to-REGmapping provided by higher layer parameter CORESET-trans-type (alsoreferred to as CORESET-CCE-to-REG-mapping); a REG bundle size, in caseof interleaved CCE-to-REG mapping, provided by higher layer parameterCORESET-REG-bundle-size; and antenna port quasi-collocation provided byhigher layer parameter CORESET-TCI-StateRefId. If the UE is notconfigured with higher layer parameter CORESET-TCI-StateRefId, the UEmay assume that the DMRS antenna port associated with PDCCH reception inthe USS and the DMRS antenna port associated with PBCH reception arequasi-collocated with respect to delay spread, Doppler spread, Dopplershift, average delay, and spatial Rx parameters.

For each serving cell and for each DCI format with CRC scrambled byC-RNTI, SPS-RNTI and/or grant-free RNTI that a UE is configured tomonitor PDCCH, the UE is configured with associations to controlresource sets. The associations may include associations to a set ofcontrol resource sets by higher layer parameter DCI-to-CORESET-map. Foreach control resource set in the set of control resource sets, theassociations may include: the number of PDCCH candidates per CCEaggregation level L by higher layer parameter CORESET-candidates-DCI; aPDCCH monitoring periodicity of kp slots by higher layer parameterCORESET-monitor-period-DCI; a PDCCH monitoring offset of op slots, where0<=o_(p)<k_(p), by higher layer parameter CORESET-monitor-offset-DCI;and a PDCCH monitoring pattern within a slot, indicating first symbol(s)of the control resource set within a slot for PDCCH monitoring, byhigher layer parameter CORESET-monitor-DCI-symbolPattern. The UE 102 mayassume that non-slot based scheduling is configured in addition toslot-based scheduling, if the UE 102 is configured with higher layerparameter CORESET-monitor-DCI-symbolPattern. The UE 102 may assume thatnon-slot based scheduling is not configured but slot-based schedulingonly, if the UE 102 is not configured with higher layer parameterCORESET-monitor-DCI-symbolPattern.

FIG. 14 illustrates PDCCH monitoring occasions for slot-based scheduling(also referred to as Type A resource allocation). PDCCH monitoringoccasions may be OFDM symbols on which the PDCCH monitoring isconfigured by a search space configuration. A search space set may beidentified for a combination of a control resource set, a DCI format (orDCI format group including DCI format having a same DCI payload size).In the example shown in FIG. 14 , two search space sets are seen, searchspace set #0 and #1. Both search space set #0 and #1 are associated witha same CORESET. The configuration of the CORESET such asCORESET-start-symb, CORESET-time-duration, CORESET-freq-dom,CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefIdapply to both search space set #0 and #1. For example,CORESET-time-duration set to 3 symbols applies to both of them. Searchspace set #0 may be associated with a certain DCI format (e.g., DCIformat 1, fallback DCI format), and search space set #1 may beassociated with another certain DCI format (e.g., DCI format 2, regularDCI format). The higher layer parameter CORESET-monitor-period-DCI isset to 2 slots for search space set #0, while the higher layer parameterCORESET-monitor-period-DCI is set to 1 slot for search space set #1.Therefore, DCI format 1 may be potentially transmitted and/or monitoredin every 2 slot, while DCI format 2 may be potentially transmittedand/or monitored in every slot.

FIG. 15 illustrates PDCCH monitoring occasions for non-slot-basedscheduling. In the example shown in FIG. 15 , two search space sets areseen, search space set #2 and #3. Both search space set #2 and #3 areassociated with a same CORESET. This CORESET may or may not be the sameCORESET as in FIG. 15 . The higher layer parametersCORESET-monitor-period-DCI for both search space set #2 and #3 are setto 1 slot.

In addition, the higher layer parametersCORESET-monitor-DCI-symbolPattern are individually configured to searchspace set #2 and #3. The higher layer parameterCORESET-monitor-DCI-symbolPattern may indicate, using a bitmap scheme,OFDM symbol(s) on which PDCCH is monitored. To be more specific, thehigher layer parameter CORESET-monitor-DCI-symbolPattern per searchspace set may include 14 bits, the 1st bit to 14^(th) bit whichcorrespond to OFDM symbol #0 to #13, respectively. Each of the bitsindicates whether or not PDCCH is monitored on the corresponding OFDMsymbol (e.g., “0” indicates no PDCCH monitoring and “1” indicates PDCCHmonitoring, or vice versa). In this example, the higher layer parametersCORESET-monitor-DCI-symbolPattern for search space set #2 indicates OFDMsymbols #0 and #7 for PDCCH monitoring, which the higher layerparameters CORESET-monitor-DCI-symbolPattern for search space set #3indicates OFDM symbols #0, #2 , #4 , #6 , #8 , #10 , #12 for PDCCHmonitoring. It is noted that these PDCCH monitoring applies to the slotthat is specified by CORESET-monitor-period-DCI andCORESET-monitor-offset-DCI.

A control-channel element may include 6 resource-element groups (REGs)where a resource-element group equals one resource block during one OFDMsymbol. Resource-element groups within a control-resource set may benumbered in increasing order in a time-first manner, starting with 0 forthe first OFDM symbol and the lowest-numbered resource block in thecontrol resource set. A UE can be configured with multiplecontrol-resource sets. Each control-resource set may be associated withone CCE-to-REG mapping only. The CCE-to-REG mapping for acontrol-resource set can be interleaved or non-interleaved, configuredby the higher-layer parameter CORESET-CCE-REG-mapping-type. The REGbundle size is configured by the higher-layer parameterCORESET-REG-bundle-size. For non-interleaved CCE-to-REG mapping, the REGbundle size is 6. For interleaved CCE-to-REG mapping, the REG bundlesize is either 2 or 6 for a CORESET with CORESET-time-duration set to 1,and the REG bundle size is either N^(CORESET) _(symb) or 6 for a CORESETwith CORESET-time-duration N^(CORESET) _(symb) set to greater than 1.The UE may assume: the same precoding in the frequency domain being usedwithin a REG bundle if the higher-layer parameterCORESET-precoder-granularity equals CORESET-REG-bundle-size; and thesame precoding in the frequency domain being used across withincontiguous RBs in CORESET if the higher-layer parameterCORESET-precoder-granularity equals the number of contiguous RBs in thefrequency domain within CORESET.

Each control resource set includes a set of CCEs numbered from 0 toN_(CCE,p,kp)−1 where N_(CCE,p,kp) is the number of CCEs in controlresource set p in monitoring period kp. The sets of PDCCH candidatesthat a UE monitors are defined in terms of PDCCH UE-specific searchspaces. A PDCCH UE-specific search space S^((L)) _(kp) at CCEaggregation level L is defined by a set of PDCCH candidates for CCEaggregation level L. L can be one of 1, 2, 4, and 8.

PDSCH and/or PUSCH RE mapping may be affected by higher layer signalingand/or layer-1 signaling such as a PDCCH with a DCI format 1 and 2. ForPDSCH, modulated complex-valued symbols may be mapped in REs which meetall of the following criteria: they are in the resource blocks assignedfor transmission; they are declared as available for PDSCH according torate matching resource set configuration and/or indication; they are notused for CSI-RS; they are not used for Phase Tracking RS (PT-RS); theyare not reserved for SS/PBCH; they are not declared as ‘reserved’.

To decode PDSCH according to a detected PDCCH, a UE may be configuredwith any of higher layer parameters: rate-match-PDSCH-resource-setincluding one or multiple reserved pairs of RBs (higher layer parameterrate-match-PDSCH-resource-RBs which is also referred to as bitmap-1) andreserved symbols (higher layer parametersrate-match-PDSCH-resource-symbols which is also referred to as bitmap-2)for which the reserved RBs apply; rate-match-resources-v-shift includingLTE-CRS-vshift(s); rate-match-resources-antenna-port including LTE-CRSantenna ports 1, 2 or 4 ports;

rate-match-CORESET including CORESET-ID(s) of CORESET configured to a UE102 for monitoring. The UE 102 may have to determine the PDSCH REmapping according to the union of provided rate-matching configurations.To decode PDSCH a UE 102 rate-matches around the REs corresponding todetected PDCCH that scheduled the PDSCH. A UE 102 may not be expected tohandle the case where PDSCH DMRS REs are over-lapping, even partially,with any RE(s) indicated by the rate-matching configurationrate-match-PDSCH-resource-set and rate-match-resources-v-shift andrate-match-resources-antenna-port and rate-match-CORESET.

If a UE 102 receives a PDSCH without receiving a corresponding PDCCH, orif the UE 102 receives a PDCCH indicating a SPS PDSCH release, the UE102 may generate one corresponding HARQ-ACK information bit. If a UE 102is not provided higher layer parameter PDSCH-CodeBlockGroupTransmission,the UE 102 may generate one HARQ-ACK information bit per transportblock. A UE 102 is not expected to be indicated to transmit HARQ-ACKinformation for more than two SPS PDSCH receptions in a same PUCCH. Foreach physical cell group, UE 102 may be configured with higher layerparameter pdsch-HARQ-ACK-Codebook which indicates PDSCH HARQ-ACKcodebook type. The PDSCH HARQ-ACK codebook may be either semi-static(also referred to as Type-1 HARQ-ACK codebook) or dynamic (also referredto as Type-2 HARQ-ACK codebook). This may be applicable to both CA andnone CA operation and may correspond to L1 parameter‘HARQ-ACK-codebook’.

A UE 102 may report HARQ-ACK information for a corresponding PDSCHreception or SPS PDSCH release only in a HARQ-ACK codebook that the UEtransmits in a slot indicated by a value of a PDSCH-to-HARQ_feedbacktiming indicator field in a corresponding DCI format (e.g. DCI format1_0 or DCI format 1_1). If the UE 102 receives the PDCCH or SPS PDSCHrelease successfully, a value of the corresponding HARQ-ACK informationbit may be basically set to ACK. If the UE 102 does not receive thePDCCH or SPS PDSCH release successfully (i.e. fails to receive it), thevalue of the corresponding HARQ-ACK information bit may be basically setto NACK. The UE 102 may report NACK value(s) for HARQ-ACK informationbit(s) in a HARQ-ACK codebook that the UE transmits in a slot notindicated by a value of a PDSCH-to-HARQ_feedback timing indicator fieldin a corresponding DCI format (e.g. DCI format 1_0 or DCI format 1_1).If the UE 102 is provided higher layer parameterpdsch-AggregationFactor, N_(PDSCH) ^(repeat) is a value ofpdsch-AggregationFactor; otherwise, N_(PDSCH) ^(repeat)=1. The UE 102may report HARQ-ACK information only for a last slot of the N_(PDSCH)^(repeat) slots.

If a UE reports HARQ-ACK information in a PUSCH or a PUCCH only for aSPS PDSCH release or only for a PDSCH reception within the M_(A,c)occasions for candidate PDSCH receptions that is scheduled by DCI format1_0 with a counter DAI field value of 1 on the PCell, the UE maydetermine a HARQ-ACK codebook only for the SPS PDSCH release or only thePDSCH reception, e.g. one-bit HARQ-ACK codebook. Otherwise, the HARQ-ACKcodebook may be more than one bit.

In some cases, a HARQ-ACK information bit may be automatically set to afixed value (e.g. NACK, or ACK) without referring to PDSCH reception orSPS PDSCH release reception. For example, if the UE is configured withpdsch-HARQ-ACK-Codebook=semi-static, the UE 102 may report NACK value(s)for HARQ-ACK information bit(s) in a HARQ-ACK codebook that the UEtransmits in a slot not indicated by a value of a PDSCH-to-HARQ_feedbacktiming indicator field in a corresponding DCI format (e.g. DCI format1_0 or DCI format 1_1).

Another case where HARQ-ACK information bit may be automatically set toa fixed value (e.g. NACK, or ACK) without referring to PDSCH receptionor SPS PDSCH release reception is that, if an occasion for a candidatePDSCH reception can be in response to a PDCCH with a DCI format (e.g.DCI format 1_1) and if higher layer parametermaxNrofCodeWordsScheduledByDCI indicates reception of two transportblocks, when the UE receives a PDSCH with one transport block, theHARQ-ACK information is associated with the first transport block andthe UE 102 may generate a NACK for the second transport block if higherlayer parameter harq-ACK-SpatialBundlingPUCCH is not provided and maygenerate HARQ-ACK information with value of ACK for the second transportblock if higher layer parameter harq-ACK-SpatialBundlingPUCCH isprovided.

Yet another case where HARQ-ACK information bit may be automatically setto a fixed value (e.g. NACK, or ACK) without referring to PDSCHreception or SPS PDSCH release reception is that, if the UE 102 isconfigured by higher layer parameter maxNrofCodeWordsScheduledByDCI withreception of two transport blocks for the active DL BWP of serving cellc, and if the UE 102 receives one transport block, the UE 102 may assumeACK for the second transport block.

Yet another case where HARQ-ACK information bit may be automatically setto a fixed value (e.g. NACK, or ACK) without referring to PDSCHreception or SPS PDSCH release reception is that the UE 102 may set toNACK value in the HARQ-ACK codebook any HARQ-ACK informationcorresponding to PDSCH reception or SPS PDSCH release scheduled by DCIformat (e.g. DCI format 1_0 or DCI format 1_1) that the UE 102 detectsin a PDCCH monitoring occasion that is after a PDCCH monitoring occasionwhere the UE detects a DCI format (e.g. DCI format 1_0 or DCI format1_1) scheduling the PUSCH transmission.

NR may support code block group based transmission(s) for PDSCH andPUSCH. If the UE 102 is provided higher layer parameterPDSCH-CodeBlockGroupTransmission for a serving cell, the UE 102 mayreceive PDSCHs that include code block groups (CBGs) of a transportblock and the UE 102 may be provided higher layer parametermaxCodeBlockGroupsPerTransportBlock indicating a maximum numberN_(HARQ-ACK) ^(CBG/T/B,max) of CBGs for generating respective HARQ-ACKinformation bits for a transport block reception for the serving cell,where for the number of C code blocks (CBs) in a transport block, the UE102 may determine the number of CBGs as N_(HARQ-ACK)^(CBG/TB)=min(N_(HARQ-ACK) ^(CBG/TB,max), C).

For CBG-based PDSCH reception, if the UE 102 successfully decodes allCGs in a given CBG of a TB, a value of the HARQ-ACK information bitcorresponding the CBG may be basically set to ACK. If the UE 102 doesnot successfully decode (i.e. fails to decode) at least one CG in thegiven CBG of the TB, a value of the HARQ-ACK information bitcorresponding the CBG may be basically set to NACK. In addition, in somecases, a HARQ-ACK information bit for a given CBG may be automaticallyset to a fixed value (e.g. NACK, or ACK) without referring to thereception of the associated CB(s).

For example, the HARQ-ACK codebook includes the N_(HARQ-ACK)^(CBG/TB,max) HARQ-ACK information bits and, if N_(HARQ-ACK)^(CBG/TB)<N_(HARQ-ACK) ^(CBG/TB,max) for a transport block, the UE 102may generate a NACK value for the last N_(HARQ-ACK)^(CBG/TB,max)−N_(HARQ-ACK) ^(CBG/TB) HARQ-ACK information bits for thetransport block in the HARQ-ACK codebook.

In another case where a HARQ-ACK information bit for a CBG isautomatically set to ACK without referring to the reception of theassociated CB(s) is that, if the UE 102 generates a HARQ-ACK codebook inresponse to a retransmission of a transport block, corresponding to asame HARQ process as a previous transmission of the transport block, theUE 102 may generate an ACK for each CBG that the UE 102 correctlydecoded in a previous transmission of the transport block.

Yet another case where a HARQ-ACK information bit for a CBG isautomatically set to a certain value without referring to the receptionof the associated CB(s) is that if the UE 102 receives a PDSCH that isscheduled by a PDCCH with DCI format (e.g. DCI format 1_0), or a SPSPDSCH, or the UE detects a SPS PDSCH release, and if the UE isconfigured with higher layer parameterpdsch-HARQ-ACK-Codebook=semi-static, the UE may repeat N_(HARQ-ACK)^(CBG/TB,max) times the HARQ-ACK information for the transport block inthe PDSCH or for the SPS PDSCH release, respectively, for generatingN_(HARQ-ACK) ^(CBG/TB,max) HARQ-ACK information bits

The 5G NR system may be operated licensed spectrum which is owned bycellular operators. Additionally and/or alternatively the 5G NR systemmay be operated in unlicensed spectrum as a complementary tool for theoperators to augment their service offering. NR-based unlicensed access(NR-U) may be applicable to below 6 GHz and above 6 GHz unlicensed bands(e.g., 5 GHz, 37 GHz, 60 GHz). NR-U cell may be operated in TDD bandswith either an LTE-based anchor cell or an NR-based anchor cell (i.e.standalone NR cell). Furthermore, standalone operation of NR-U inunlicensed spectrum may also be possible.

In order to ensure a fair co-existence with another NR-U node and/oranother radio access technology (RAT) node such as wireless LAN node,the gNB 160 and/or the UE 102 may have to perform Listen Before Talk(LBT) procedure before their transmissions. LBT procedure is alsoreferred to as Channel Access procedure. There may be several types ofChannel Access (CA) procedures.

FIG. 16 shows the first type of Channel Access procedure. The first typeof Channel Access procedure may be used for downlink transmission(s)including PDSCH and PDCCH. The gNB 160 may transmit a transmissionincluding PDSCH and PDCCH on a carrier on which NR-U cell(s)transmission(s) are performed, after first sensing the channel to beidle during the CA slot durations of a defer duration T_(d); and afterthe counter N is zero in step 4. The counter N is adjusted by sensingthe channel for additional CA slot duration(s) according to the Step S1to step S6. In Step S1, the gNB 160 may set N=N_(init), where N_(init)is a random number uniformly distributed between 0 and CW_(p), and go toStep S4. In Step S2, if N>0 and the gNB 160 chooses to decrement thecounter, the gNB 160 may set N=N−1. In Step S3, the gNB 160 may sensethe channel for an additional CA slot duration, and if the additional CAslot duration is idle, go to Step S4, otherwise go to Step S5. In StepS4, if N=0, the gNB 160 may stop, otherwise go to Step S2. In Step S5,the gNB 160 may sense the channel until either a busy CA slot isdetected within an additional defer duration T_(d) or all the CA slotsof the additional defer duration T_(d) are detected to be idle. In StepS6, if the channel is sensed to be idle during all the CA slot durationsof the additional defer duration T_(d), the gNB 160 may go to Step S4,otherwise go to Step S5.

FIG. 17 shows an example of deferment of transmission. If the gNB 160has not transmitted a transmission including PDSCH/PDCCH on a carrier onwhich NR-U cell(s) transmission(s) are performed after Step S4 in thisprocedure, the gNB 160 may transmit a transmission including PDSCH/PDCCHon the carrier, if the channel is sensed to be idle at least in a CAslot duration T_(sl) when the gNB 160 is ready to transmit PDSCH/PDCCHand if the channel has been sensed to be idle during all the CA slotdurations of a defer duration T_(d) immediately before thistransmission. If the channel has not been sensed to be idle in a s CAlot duration T_(sl) when the gNB 160 first senses the channel after itis ready to transmit or if the channel has been sensed to be not idleduring any of the CA slot durations of a defer duration T_(d)immediately before this intended transmission, the gNB 160 may proceedto Step S1 after sensing the channel to be idle during the CA slotdurations of a defer duration T_(d). The defer duration T_(d) mayconsist of duration T_(f)=16 us immediately followed by m_(p)consecutive CA slot durations where each slot duration is T_(sl)=9 us,and T_(f) includes an idle CA slot duration T_(sl) at start of T_(f). Aslot duration T_(sl) may be considered to be idle if the gNB 160 sensesthe channel during the CA slot duration, and the power detected by thegNB 160 for at least 4 us within the CA slot duration is less thanenergy detection threshold X_(Thresh). Otherwise, the CA slot durationT_(sl) may be considered to be busy. By using the above-describedtransmission deferment, more than one cells of which locations aregeometrically separated may be able to obtain channel accesssuccessfully at the same time, and therefore frequency reuse among thecells can be achieved.

CW_(min,p)≤CW_(p)≤CW_(max,p) is the contention window. CW_(p) adjustmentmay be performed by the gNB 160. CW_(min,p) and CW_(max,p) may be chosenbefore Step S1 of the above-described procedure. m_(p), CW_(min,p), andCW_(max,p) may be derived based on channel access priority classassociated with the gNB transmission.

FIG. 18 shows an example of channel access priority class for downlinktransmission(s). In this example, there are 4 classes, and lower indexmay correspond to higher priority. For each class, a parameter set forthe channel access procedure is defined. The parameter set for class pmay include m_(p), CW_(min,p), CW_(max,p), T_(mcot,p), and allowedCW_(p) sizes, where T_(mcot,p) is referred to as maximum channeloccupancy time (MCOT).

The gNB 160 getting channel access with priority class p may not beallowed to continuously transmit on the carrier on which NR-U cell(s)transmission(s) are performed, for a period exceeding T_(mcot,p).

Similarly, the UE 102 may use the first type of Channel Access procedurefor uplink transmission(s) including PUSCH and/or PUCCH. Theabove-described Channel access procedure including Step S1 to Step S6may be used with “gNB 160” replaced by “UE102”, with “PDSCH/PDCCH”replaced by “PUSCH/PUCCH/SRS”, and with uplink channel access priorityclass. FIG. 19 shows an example of channel access priority class foruplink transmission(s). When the first type of Channel Access procedureis used for uplink transmission, it may also be referred to as Type-1 ULChannel Access procedure.

FIG. 20 shows the second type of Channel Access procedure. The secondtype of Channel Access procedure may be used for downlinktransmission(s) including discovery signal transmission(s) and notincluding PDSCH. The discovery signal may include SS/PBCH(s), CSI-RS(s)and/or control resource set(s). The second type of Channel Accessprocedure may make the channel access easier than the first type, sincethe discovery signal may not occupy a long transmission durationcompared with a PDSCH transmission. An gNB 160 may transmit atransmission including discovery signal but not including PDSCH on acarrier on which NR-U cell(s) transmission(s) are performed immediatelyafter sensing the channel to be idle for at least a sensing intervalT_(drs)=25 us and if the duration of the transmission is less than 1 ms.T_(drs) may consist of a duration T_(f)=16 us immediately followed byone CA slot duration T_(sl)=9 us and T_(f) includes an idle CA slotduration T_(sl) at start of T_(f). The channel is considered to be idlefor T_(drs) if it is sensed to be idle during the slot durations ofT_(drs).

FIG. 21 shows the third type of Channel Access procedure. Channelsensing scheme of the third type of Channel Access procedure is almostthe same as of the second type of Channel Access procedure. The thirdtype of Channel Access procedure may be used for uplink transmission(s)which is to be transmitted inside of COT obtained by the first typechannel access procedure at the gNB 160 side. In the example, the gNB160 performs the first type channel access procedure right before aCommon Control-PDCCH (CC-PDCCH) transmission. CC-PDCCH may also bereferred to as PDCCH with CRC scrambled by common control-RNTI(CC-RNTI). In a DCI format carried by the CC-PDCCH may include severalbit fields including bit field(s) for indicating “UL offset” and “ULduration”. If UL offset l and duration d are indicated by the CC-PDCCHfor subframe n, the UE 102 is not required to receive any downlinkphysical channels and/or physical signals in slot(s) n+l+i with i=0, 1,. . . , d−1, and those slot(s) may have to be covered by the MCOT whichwas obtained by the channel access for the CC-PDCCH transmission at gNB160 side. If the UE uses Type 2 channel access procedure for atransmission including PUSCH, the UE may be allowed to transmit thetransmission including PUSCH immediately after sensing the channel to beidle for at least a sensing interval T_(short_ul)=25 us orT_(short_ul)=16 us. They may be considered as a same channel accessprocedure types but with different durations. Alternatively, Type 2channel access procedure with T_(short_ul)=25 us may also be referred toas uplink Type 2A channel access procedure and Type 2 channel accessprocedure with T_(short_ul)=16 us may also be referred to as uplink Type2B channel access procedure. In this case, they may be considered as twodifferent channel access procedure types. T_(short_ul) consists of aduration T_(f)=16 us immediately followed by one CA slot durationT_(sl)=9 us and T_(f) includes an idle CA slot duration T_(sl) at startof T_(f). The channel is considered to be idle for T_(short_ul) if it issensed to be idle during the CA slot durations of T_(short_ul). Thethird type of Channel Access procedure may also be referred to as Type-2UL Channel Access procedure. Note that the other type of PDCCH (e.g.PDCCH with DCI format 0_0, 0_1, 0_2, 0_3, 1_0, 1_1, 1_2, 1_3) for slot nmay also indicate “UL offset” and “UL duration”. In this case, the UEmay also be allowed to use the third type of Channel Access procedure,if configured.

FIG. 22 shows the fourth type of Channel Access procedure. Channelsensing scheme of the fourth type of Channel Access procedure is almostthe same as of the second and third types of Channel Access procedure.The fourth type of Channel Access procedure may be used for downlinktransmission(s) which includes PUSCH but does not include PDSCH and isto be transmitted inside of COT obtained by the first type channelaccess procedure at the UE 102 side. If a PUSCH transmission indicatesCOT sharing, an gNB 160 may be allowed to transmit a transmissionincluding PDCCH but not including PDSCH on the same carrier immediatelyafter sensing the channel to be idle for at least a sensing intervalT_(pdcch)=25 us, if the duration of the PDCCH is less than or equal totwo OFDM symbols length and it shall contain at least Downlink FeedbackInformation (DFI) or UL grant to the UE from which the PUSCHtransmission indicating COT sharing was received. T_(pdcch) consists ofa duration T_(f)=16 us immediately followed by one slot durationT_(sl)=9 us and T_(f) includes an idle slot duration T_(sl) at start ofT_(f). The channel is considered to be idle for T_(pdcch) if it issensed to be idle during the slot durations of T_(pdcch).

In order to avoid collisions with transmissions from other nodes,contention window (CW) size may change depending on how many timescollisions occur or equivalent. If a collision is observed at a node,the node may have to increase the CW size. If any collision is notobserved, the node may be allowed to reduce the CW size. FIG. 23 showsan example of CW size adjustment. This example assumes that the numberof available CW size is 7, i.e. CW #0 to CW #6. If a collision isobserved, CW size is increased to the CW size with the next higherindex, except for the CW_(max) in which case the CW size is kept asCW_(max). If any collision is not observed, the CW size may fallback toCW_(min) irrespective of the previous CW size.

A possible metric for the gNB's decision on whether or not the collisionoccurs for PDSCH may be HARQ-ACK feedback from the UE 102. Anotherpossible metric for the gNB's decision on whether or not the collisionoccurs in PDCCH may be PUSCH from the UE 102. For uplink, a possiblemetric for the UE's decision on whether or not the collision occurs forPUSCH may be whether or not uplink retransmission is requested.

FIG. 24 shows an example of LBT for a transmission with a directionalbeam. The gNB 160 may perform transmission beam sweeping with multiplenarrow Tx beams (e.g. Tx beam #1, #2 and #3). Immediately before asignal transmission with any Tx beam, the gNB 160 may have to performLBT. In this example, the gNB 160 performs channel sensing by using awider beam (Rx beam #0) in horizontal plane (e.g. omni-directional Rxbeam). The LBT parameters (counter, CWS, channel access class, COT, andso on) may be managed per node. For example, counter and CWS may bemanaged per node. In this case, once the counter reaches zero, the gNB160 may be allowed to perform transmission with any of the Tx beams, anda single CWS is maintained with referring to collisions (e.g. NACKs) onall of the Tx beams.

Additionally and/or alternatively, some linkage from Tx beam used for atransmission to Rx beam used for channel sensing for the transmission,or vice versa, may be defined. For example; each of the Tx beam #1, #2and #3 corresponds to the Rx beam #0. In this case, the LBT parametersmay be managed per Rx beam. For example, counter and CWS may be managedper node. Once the counter for a given Rx beam reaches zero, the gNB 160may be allowed to perform transmission with any of the Tx beams whichare linked to the given Rx beam, and a single CWS for the given Rx beamis maintained with referring to collisions on all of the Tx beams whichare linked to the given Rx beam. COT may be figured per Rx beam. Withinthe COT for a given Rx beam, the gNB 160 may be allowed, subject toCat-1 or Cat-2 LBT, to perform transmissions using any of the Tx beamswhich correspond to the given Rx beam. Alternatively, either the counteror the CWS may be managed per Rx beam while the other one may be managedper node. For example, the counter is managed per Rx beam, and once thecounter reaches zero, the gNB 160 may be allowed to perform atransmission with any of the Tx beams which are linked to the Rx beam.On the other hand, collisions on all of Tx beams (including Tx beam #1,#2 and #3 and any other beams of the gNB160) may be considered for CWSadjustment for the Rx beam #0.

Cat-1 LBT is a channel access procedure without channel sensing. Cat-2LBT is a channel access procedure with one shot channel sensing. Cat-2LBT may also be referred to as Type-2 channel access procedure. Cat-2LBT may be further separated into two types in terms of a channelsensing slot length, the first one is Cat-2 LBT with 25 μs channelsensing slot and the other is Cat-2 LBT with 16 μs channel sensing slot.Cat-1 and Cat-2 LBTs may be allowed only inside COT. Cat-2 LBT with 16μs channel sensing slot may be allowed to be used if a gap length fromthe timing when the channel gets idle is equal to 16 μs. Cat-2 LBT with25 μs channel sensing slot may be allowed to be used if a gap lengthfrom the timing when the channel gets idle is equal to or longer than 25μs. Cat-3 LBT is a channel access procedure with random backoff with afixed CW side. Cat-4 LBT is a channel access procedure with randombackoff with an adaptive CW side. Cat-4 LBT may also be referred to asType-1 channel access procedure.

Tx beams may correspond to some physical channels or physical signals.For example, each Tx beam may correspond to a respective source ofquasi-co-location (QCL) assumption. The sources of QCL assumption mayinclude SS/PBCH, CSI-RS, PT-RS, NR-U discovery signal/channel which maycomprise SS/PBCH, and the like. Therefore, it is noted that theabove-described “Tx beam” can be interpreted as the correspondingphysical channel or physical signal. Alternatively and/or additionally,the Tx beam may correspond to some transmission antenna configuration,e.g. a weight vector for a transmission antenna array. In this case, theabove-described “Tx beam” can be interpreted as the correspondingantenna configuration. Similarly, the Rx beam may correspond to somereception antenna configuration, e.g. a weight vector for a receptionantenna array. In this case, the above-described “Rx beam” can beinterpreted as the corresponding antenna configuration.

If beam forming gain for channel sensing is different from one for thecorresponding transmission, threshold for the channel sensing may needto be adjusted. For example, the antenna gain ratio between Rx antennaconfiguration and. Tx antenna configuration for a given direction (e.g.the direction to the target UE, the center direction of the Tx beam mainlobe, the direction of the peak of the Tx beam main lobe) may be usedfor the threshold adjustment. More specifically, if the antenna gain ofthe center direction of Tx beam #1 is 20 dBi and the antenna gain of thesame direction of Rx beam #0 (which is linked from the Tx beam #1) is 2dBi, the threshold value for the channel sensing using the Rx beam #0may be decreased with 18 dB, compared with a non-directionaltransmission case.

FIG. 25 shows an example of LBT for a transmission with a directionalbeam. The gNB 160 may be able to use multiple narrow Tx beams (e.g. Txbeam #1, #2 and #3) for transmissions as well as multiple narrow Rxbeams (e.g. Rx beam #1, #2 and #3) for receptions. Immediately before asignal transmission with any Tx beam, the gNB 160 may have to performLBT. Some linkage (e.g. 1-to-1 mapping) from Tx beam used for atransmission to Rx beam used for channel sensing for the transmission,or vice versa, may be defined. For example, the Tx beam #1, #2 and #3correspond to the Rx beam #1, #2 and #3, respectively. Immediatelybefore a transmission with a given Tx beam, LBT may, have to beperformed by using the Rx beam which is linked from the given Tx beam.In other words, once the gNB 160 obtains a channel by using the LBT witha given Rx beam, the gNB 160 may be allowed to perform a transmissionwith the Tx beam which is linked to the given Rx beam. LBT parametersmay be managed per Tx beam. COT may be figured per Tx beam. Within theCOT for a given Tx beam, the gNB 160 may be allowed, subject to Cat-1 orCat-2 LBT, to perform transmissions using the given Tx beam.Additionally, some of the LBT parameters may be managed per node. Forexample, a single counter may be generated and updated for each Tx beam,while a single CWS per node may be adjusted by considering collisions onall of the Tx beams. The COT may be figured per node. Within the COT,the gNB 160 may be allowed, subject to Cat-1 or Cat-2 LBT, to performtransmissions using any of the Tx beams.

FIG. 26 shows an example of sub-band configuration. A NR band mayinclude one or more NR carriers (also referred to as just carrier). Acarrier may include one or more BWPs. BWP #0 (also referred to asinitial BWP or initial DL BWP, which may be configured by MasterInformation Block (MIB), System Information Block type 1 (SIB1), orequivalent for PCell) may have 20 MHz bandwidth. The other BWPs may havebandwidth of multiple of 20 MHz. Each sub-band may comprise 20 MHz or amultiple of 20 MHz bandwidth and is defined within a BWP. BWP #0 mayconsist of a single 20 MHz sub-band. Any other BWP may consist of one ormore sub-bands. The sub-band may be a unit of frequency scheduling. Thesub-band may also be referred to as sub-channel, channel accessbandwidth, or the like. A higher layer configuration about a BWP mayinclude a configuration of sub-band(s) in the BWP. Alternatively, thesub-band(s) may be configured by using frequency domain resourceallocations in CORESET configurations. The sub-band may be an upperlimit of the resources which is schedulable by a single DCI. In otherwords, PDSCH/PUSCH resource allocation is defined within a sub-band andnot across a sub-band boundary. The sub-band may be a unit of LBT. Thesub-band may be a unit of CORESET configuration. CORESET frequencyresource allocation is defined within a sub-band and not across asub-band boundary.

Additionally and/or alternatively, CORESET configuration may containsinformation for indicating frequency repetition of the CORESET. Forexample, if CORESET configuration contains an information element forfrequency repetition, the frequency repetition of the CORESET may beconsidered to be enabled. if CORESET configuration does not contain theinformation element for frequency repetition, the frequency repetitionof the CORESET may be considered to be disabled. The information elementfor frequency repetition may include one or more of 1) frequency domainrepetition factor (i.e. the number of frequency domain repetitions), 2)frequency domain interval between adjacent repetitions, etc. If UE 102is configured with the repetition enabled, the UE 102 may assume thesame set of PDCCHs are transmitted among those repeated CORESETs.

PDCCH in a CORESET in a given sub-band may be able to schedule a PDSCHonly in the same sub-band. For example, DCI format(s) used for thescheduling of PDSCH/PUSCH in a NR-U cell may include a frequency domainresource assignment field−|log 2 (N(N+1)/2)| bits, where N may be thesize of the bandwidth of the sub-band where the PDCCH carrying the DCIis detected, in case the DCI is detected in UE specific search space andsatisfying requirement(s) on the total number of different DCI sizes.Otherwise (e.g. in case the DCI is detected in common search space), Nmay be the size of the bandwidth of the sub-band which corresponds to aninitial BWP (i.e. BWP #0). N may be expressed in RB number.

In a BWP, the gNB 160 may perform channel sensing in every sub-band andmay transmit a signal (PDCCH, PDSCH, etc) in the sub-band(s) on whichthe gNB 160 gets a channel access successfully. The UE 102 may be ableto monitor PDCCHs in multiple CORESET which correspond to differentsub-bands. The gNB 160 may manage the LBT parameters per sub-band,alternatively per BWP, or yet alternatively per cell. Additionallyand/or alternatively some of the LBT parameters may be managed persub-band, which the others may be managed differently (e.g. per BWP orper cell).

In a BWP, the UE 102 may perform channel sensing in every sub-band andmay transmit a signal (PUCCH, PUSCH, etc) in the sub-band(s) on whichthe UE 102 gets a channel access successfully. The gNB 160 may be ableto monitor the signal in every sub-bands. The UE 102 may manage the LBTparameters per sub-band, alternatively per BWP, or yet alternatively percell. Additionally and/or alternatively some of the LBT parameters maybe managed per sub-band, which the others may be managed differently(e.g. per BWP or per cell).

Additionally and/or alternatively, PDCCH in each sub-band may be able toschedule a PDSCH in the whole bandwidth of the BWP. For example, DCIformat(s) used for the scheduling of PDSCH/PUSCH in a NR-U cell mayinclude a frequency domain resource assignment field−|log 2 (N(N+1)/2)|bits, where N may be the size of the bandwidth of the active BWP. In theBWP, the gNB 160 may prepare a PDSCH/PUSCH assuming that the wholebandwidth of the BWP is available for the PDSCH/PUSCH transmission. ThegNB 160 may perform channel sensing in every sub-band and may transmitthe prepared PDSCH only on the sub-band(s) where the LBT was successful.On the sub-band(s) where the LBT was failed, the PDSCH resources (e.g.REs or RBs) may have to be punctured (i.e. the PDSCH is not mapped tothe physical resources) so that the PDSCH transmission does not happenin those sub-band(s). Regarding PDCCH which schedules the PDSCH,multiples PDCCHs scheduling the same PDSCH may be prepared. These PDCCHsmay be assumed to be mapped in different sub-bands in the BWP. ThePDCCH(s) in the sub-band(s) on which the gNB 160 gets a channel accesssuccessfully may be transmitted, while The PDCCH(s) in the sub-band(s)on which the gNB 160 does not get a channel access successfully may notbe transmitted.

In this case, if the gNB 160 gets the channel access in more than onesub-band, the UE 102 may detect more than one PDCCHs that schedule thesame. PDSCH. Scheduling the same PDSCH may mean the DCIs in the PDCCHhave the same value in every information field and CRC. Alternatively,it may mean the DCIs in the PDCCH indicate the same PDSCH parameter set,e.g. allocated resources, counter DAI, PUCCH resource, etc. Yetalternatively, it may mean those PDCCHs are repeated among the repeatedCORESETs (i.e. CORESETS with the frequency domain repetition). If the UE102 may detect more than one PDCCHs that schedule the same PDSCH, the UEmay have to discard the PDCCHs except for one of them. In other words,only one PDCCH is considered to be valid, while all the other detectedPDCCHs are considered to be invalid. Alternatively, the UE 102 mayconsider those multiple detected PDCCHs as a single detected PDCCH, andthe duplicated indications of the multiple detected PDCCHs may applyonly once.

The above-described principle may apply to the other type of DCI (e.g.DCI format 0_0, 0_1, 2_0, 2_1, 2_2, 2_3) than the one scheduling PDSCH.For example, the gNB 160 may transmit multiple PDCCHs with DCI format2_2 in the multiple sub-bands in the BWP. If the UE 102 detects themultiple PDCCHs with DCI format 2_2 in the multiple sub-bands, the TPCcommand of only one of the PDCCHs with the DCI format 2_2 may apply andthe TPC command(s) of the other PDCCHs may not apply.

The frequency domain resource assignment field in the DCI in the PDCCHmay indicate allocated resources (e.g. resource blocks) comprise theresources on the sub-band(s) to which the gNB 160 does not actually mapthe PDSCH due to a channel access failure. Without any supplementaryinformation, the UE 102 detecting the DCI may assume that the PDSCH ismapped to the resources in those sub-band(s).

Alternatively, the UE 102 may utilize some supplementary information sothat the UE 102 can perform PDSCH decoding assuming that the PDSCH isnot mapped to the resource in those sub-band(s). The supplementaryinformation may be results of PDCCH detections in the sub-bands.Additionally and/or alternatively, the supplementary information may beinformation provided by CC-PDCCH or SFI PDCCH. Additionally and/oralternatively, the supplementary information may be information providedby DCI format 2_1 (also referred to as pre-emption indication).

Based on the results of PDCCH detections in the sub-bands, the UE 102may perform PDSCH decoding assuming that the PDSCH is not mapped to theresource in those sub-band(s). More specifically, for example, the UE102 configured with the repetition of the CORESET, the UE 102 may assumemultiple PDCCHs scheduling a single PDSCH are transmitted in allrepetitions of the CORESET. If the UE 102 does not detect the PDCCH in agiven sub-band, the UE 102 may assume that the scheduled PDSCH resourcesin the sub-band are not available for the PDSCH transmission and thatthe PDSCH is punctured (i.e. prepared to be mapped but not actuallymapped) on those PDSCH resources. On the other hand, if the UE 102detects the PDCCH in a given sub-band, the UE 102 may assume thescheduled PDSCH resources in the sub-band are available for the PDSCHtransmission.

Based on the information provided by CC-PDCCH or SFI PDCCH, the UE 102may perform PDSCH decoding assuming that the PDSCH is not mapped to theresource in those sub-band(s). For example, SFI PDCCH (e.g. PDCCH withDCI format 2_0 or PDCCH with DCI format which indicates slot format(s))which indicates a slot format may be transmitted in every sub-band in aBWP. A reference subcarrier spacing configuration μ_(ref) may beconfigured by higher layer parameter. Each SFI PDCCH may indicate a slotformat and/or COT structure in the respective sub-band where the SFIPDCCH is mapped.

Two transmission schemes may be supported for PUSCH: codebook basedtransmission and non-codebook based transmission. For codebook basedtransmission, the gNB 160 may provide the UE with a transmit precodingmatrix indication in the DCI. The UE 102 may use the indication toselect the PUSCH transmit precoder from the codebook. For non-codebookbased transmission, the UE 102 may determine its PUSCH precoder based onwideband SRI field from the DCI. A closed loop DMRS based spatialmultiplexing may be supported for PUSCH. For a given UE 102, up to 4layer transmissions may be supported. The number of code words may beone. When transform precoding is used, only a single MIMO layertransmission may be supported. Transmission durations from 1 to 14symbols in a slot may be supported. Aggregation of multiple slots withTB repetition may be supported. Two types of frequency hopping may besupported, intra-slot frequency hopping, and in case of slotaggregation, inter-slot frequency hopping. PUSCH may be scheduled withDCI on PDCCH, or a semi-static configured grant may be provided overRRC, where two types of operation may be supported: the first PUSCH istriggered with a DCI, with subsequent PUSCH transmissions following theRRC configuration and scheduling received on the DCI, or the PUSCH istriggered by data arrival to the UE's transmit buffer and the PUSCHtransmissions follow the RRC configuration. In the uplink, the gNB 160can dynamically allocate resources to UEs 102 via the C-RNTI onPDCCH(s). A UE 102 may always monitor the PDCCH(s) in order to findpossible grants for uplink transmission when its downlink reception isenabled (activity governed by DRX when configured). When CA isconfigured, the same C-RNTI may apply to all serving cells.

A UE may upon detection of a PDCCH with a configured DCI format 0_0 or0_1 transmit the corresponding PUSCH as indicated by that DCI. Upondetection of a DCI format 0_1 with “UL-SCH indicator” set to “0” andwith a non-zero “CSI request” where the associated “reportQuantity” inCSI-ReportConfig set to “none” for all CSI report(s) triggered by “CSIrequest” in this DCI format 0_1, the UE may ignore all fields in thisDCI except the “CSI request” and the UE may not transmit thecorresponding PUSCH as indicated by this DCI format 0_1. For any HARQprocess ID(s) in a given scheduled cell, the UE may not be expected totransmit a PUSCH that overlaps in time with another PUSCH. For any twoHARQ process IDs in a given scheduled cell, if the UE is scheduled tostart a first PUSCH transmission starting in symbol j by a PDCCH endingin symbol i, the UE may not be expected to be scheduled to transmit aPUSCH starting earlier than the end of the first PUSCH by a PDCCH thatends later than symbol i. The UE may not be expected to be scheduled totransmit another PUSCH by DCI format 0_0 or 0_1 scrambled by C-RNTI orMCS-C-RNTI for a given HARQ process until after the end of the expectedtransmission of the last PUSCH for that HARQ process.

In the PDCCH monitoring occasion which is tied to the detectedtriggering signal, SFI using DCI format 2_0 (also referred to as SFIPDCCH) or common control-PDCCH (CC-PDCCH) or equivalent may bemonitored. Unlike NR operation in license band, the SFI for NR-U maysupport only up to one DL-to-UL switching point.

An RRC message (e.g. a dedicated RRC message, a common RRC message, or abroadcasted RRC message) may contain an information element forconfiguring one or more (e.g. less than or equal to the number ofconfigured serving cells) SFI combination set(s), which may also bereferred to as SlotFormatCombinationsPerCell. The RRC message may alsocontain an information element for configurating a set of one or more(e.g. N) slot format combination configuration(s), which is referred toas SFI combination(s) or as slotFormatCombinations. Each of the slotformat combination configuration(s) may include a slot formatcombination and a slot format combination ID. Each of the SFIcombination set(s) may apply to a respective cell or to a respective LBTsub-band. The configuration of each of the SFI combination set(s) mayinclude a serving cell ID (or LBT sub-band ID) which is the ID of theserving cell for which the slotFormatCombinations are applicable,subcarrier spacing which is a reference subcarrier spacing for this SlotFormat Combination, one or more (e.g. N, an integer whose value is up to512) slot format combination ID(s), a position in DCI for specifying the(starting) position (bit) of the slotFormatCombinationId (SFI-Index) forthis serving cell (servingCellId) within the DCI payload. Each entry ofthe one or more slot format combination(s) may include a slot formatcombination ID and a combination of slot format(s) for one or more (e.g.M_(i) for the SFI combination i (i=1, 2, . . . , N), M_(i) being aninteger whose value is up to 256) consecutive slot(s). The number ofslot formats indicated by a respective entry may be same or differentfrom the one of another entry.

The DCI format carried by the GC-PDCCH may contain a bit field (alsoreferred to as an SFI-index field) for indicate one entry out of theconfigured slot format combination(s). The bit field size may bedetermined by using the number of the configured slot formatcombination(s). The SFI-index field value in the DCI format indicates toa UE a slot format for each slot in a number of slots for each DL BWP oreach UL BWP starting from a slot where the UE detects the DCI format. Ina non NR-U serving cell (i.e. NR serving cell operated in a licenseband), the number of slots may be equal to or larger than a PDCCHmonitoring periodicity for DCI format carrying the SFI. In an NR-Userving cell, the number of slots may be allowed to be smaller than aPDCCH monitoring periodicity for DCI format carrying the SFI. TheSFI-index field includes {┌log₂(maxSFIinde x+1)┐,1} bits wheremaxSFIindex is the maximum value of the values provided by correspondingslotFormatCombinationId. A slot format is identified by a correspondingformat index as provided in Table 1 where ‘D’ denotes a downlink symbol,‘U’ denotes an uplink symbol, and ‘F’ denotes a flexible symbol. TheSFI-index field set to n may indicate slot formats of the M_(n) slotsstarting with the slot where the UE 102 detects the DCI format, and eachslot format included in the slot format combination with the slot formatcombination ID equal to n corresponds to a respective slot within theM_(n) slots. The slot formats in Table 1 may be applicable to NR-Userving cells as well as non NR-U serving cells.

TABLE 1 Slot formats. Symbol number in a slot Format 0 1 2 3 4 5 6 7 8 910 11 12 13 0 D D D D D D D D D D D D D D 1 U U U U U U U U U U U U U U2 F F F F F F F F F F F F F F 3 D D D D D D D D D D D D D F 4 D D D D DD D D D D D D F F 5 D D D D D D D D D D D F F F 6 D D D D D D D D D D FF F F 7 D D D D D D D D D F F F F F 8 F F F F F F F F F F F F F U 9 F FF F F F F F F F F F U U 10 F U U U U U U U U U U U U U 11 F F U U U U UU U U U U U U 12 F F F U U U U U U U U U U U 13 F F F F U U U U U U U UU U 14 F F F F F U U U U U U U U U 15 F F F F F F U U U U U U U U 16 D FF F F F F F F F F F F F 17 D D F F F F F F F F F F F F 18 D D D F F F FF F F F F F F 19 D F F F F F F F F F F F F U 20 D D F F F F F F F F F FF U 21 D D D F F F F F F F F F F U 22 D F F F F F F F F F F F U U 23 D DF F F F F F F F F F U U 24 D D D F F F F F F F F F U U 25 D F F F F F FF F F F U U U 26 D D F F F F F F F F F U U U 27 D D D F F F F F F F F UU U 28 D D D D D D D D D D D D F U 29 D D D D D D D D D D D F F U 30 D DD D D D D D D D F F F U 31 D D D D D D D D D D D F U U 32 D D D D D D DD D D F F U U 33 D D D D D D D D D F F F U U 34 D F U U U U U U U U U UU U 35 D D F U U U U U U U U U U U 36 D D D F U U U U U U U U U U 37 D FF U U U U U U U U U U U 38 D D F F U U U U U U U U U U 39 D D D F F U UU U U U U U U 40 D F F F U U U U U U U U U U 41 D D F F F U U U U U U UU U 42 D D D F F F U U U U U U U U 43 D D D D D D D D D F F F F U 44 D DD D D D F F F F F F U U 45 D D D D D D F F U U U U U U 46 D D D D D F UD D D D D F U 47 D D F U U U U D D F U U U U 48 D F U U U U U D F U U UU U 49 D D D D F F U D D D D F F U 50 D D F F U U U D D F F U U U 51 D FF U U U U D F F U U U U 52 D F F F F F U D F F F F F U 53 D D F F F F UD D F F F F U 54 F F F F F F F D D D D D D D 55 D D F F F U U U D D D DD D 56-254 Reserved 255 UE may determine the slot format for the slotbased on TDD-UL-DL-ConfigurationCommon, or TDD-UL-DL-ConfigDedicatedand, if any, on detected DCI formats

GC-PDCCH carrying SFI may be applicable to a BWP comprising of more thanone LBT sub-bands, where an operation of a BWP having more than one LBTsub-bands may be also referred to as a wideband operation.

FIG. 27 shows an example of an SFI configuration and an SFI signaling.In this example, a COT includes an initial partial DL slot followed by 4full DL slot, a special slot (e.g. slot format #28 in Table 1) and then2 full UL slot, where the special slot is a slot including DL partfollowed by a gap, and then UL part. The slots of which SFIs areindicated by a single SFI combination may correspond to a single COT.The gNB 160 may provide an RRC configuration for configuring multipleSFI combinations. Some of the SFI combinations may indicate a same DL/ULconfiguration of the COT but may correspond to different GC-PDCCHtransmission timings and GC-PDCCH monitoring occasions. Before detectionof the GC-PDCCH in slot 1 (i.e. the starting slot of the COT), the UE102 has not detected any GC-PDCCH of which the SFI indicates GC-PDCCHmonitoring occasion in a middle of the slot 1. Therefore, the UE 102 maymonitor GC-PDCCH on the GC-PDCCH monitoring occasion in a middle of theslot 1. If the UE 102 detects GC-PDCCH in a middle of the slot 1, the UE102 may assume there is an initial partial slot in the slot 1, and theinitial partial slot includes the detected GC-PDCCH. The value of theSFI-index field of the GC-PDCCH in the initial partial slot may indicateSFI combination #0 which consists of SFI #0 for slot 1 (i.e. the initialpartial slot), SFI #0 for slots 2, 3, 4 and 5, SFI #28 for slot 6, andSFI #1 for slots 7 and 8. The UE 102 may be aware of the slot 1 is aninitial partial slot, because the UE 102 has detected the GC-PDCCH in amiddle of the slot 1. Therefore, the UE 102 may assume the OFDM symbolslocated before the GC-PDCCH within the slot 1 are not occupied (e.g.assumed to be indicated as Flexible by the GC-PDCCH) by the transmissioncontaining the GC-PDCCH, even though the signaled slot format for theslot 1 indicates those symbols are DL symbols. The value of theSFI-index field of the GC-PDCCH in the slot 2 may indicate SFIcombination #1 which consists of SFI #0 for slots 2, 3, 4 and 5, SFI #28for slot 6, and SFI #1 for slots 7 and 8. The same principle may applyto the GC-PDCCHs in the slots 3 to 8. Alternatively and/or additionally,the initial partial slot may be indicated by a slot format. For example,the Table 1 may additionally include a single slot format which indicateat least one OFDM symbol in a slot is not occupied by the currenttransmission while the ending part of the same slot is occupied by thecurrent transmission. In another example, the Table 1 may additionallyinclude multiple slot formats each of which indicates at least one OFDMsymbol in a slot is not occupied by the current transmission while theending part of the same slot is occupied by the current transmission,and the multiple slot formats may correspond to different numbers ofunoccupied (e.g. Flexible) OFDM symbols at the beginning part of theslot and/or different numbers of occupied (e.g. DL) OFDM symbols at theending part of the slot. The additional entries described in Table 2 maybe added by overriding of reserved entries in Table 1. Alternatively,the additional entries may be added by overriding of all or some of theTable-1 entries 46 to 54 which correspond to UL-to-DL switching in amiddle of the slot. The slot formats in Table 2 may be applicable toNR-U serving cells but not to non NR-U serving cells. If the servingcell is NR-U, the additional entries can be used. Otherwise, the UE 102may use the entries in Table 1 only. Alternatively, the use of theadditional entries may be configured by RRC signaling. In this case, ifthe RRC configuration is provided, the additional entries can be used.Otherwise the UE 102 may use the entries in Table 1 only.

TABLE 2 Additional slot formats. Symbol number in a slot Format 0 1 2 34 5 6 7 8 9 10 11 12 13 W0 F D D D D D D D D D D D D D W1 F F D D D D DD D D D D D D W2 F F F D D D D D D D D D D D W3 F F F F D D D D D D D DD D W4 F F F F F D D D D D D D D D W5 F F F F F F D D D D D D D D W6 F FF F F F F F D D D D D D W7 F F F F F F F F F D D D D D W8 F F F F F F FF F F D D D D W9 F F F F F F F F F F F D D D W10 F F F F F F F F F F F FD D W11 F F F F F F F F F F F F F D

FIG. 28 shows an example of an SFI configuration and an SFI signaling.In this example, a COT includes an initial partial DL slot followed by 4full DL slot, a special slot (e.g. slot format #28 in Table 1) and then2 full UL slot. The gNB 160 may provide an RRC configuration forconfiguring multiple SFI combinations. One of the SFI combinations mayindicate a DL/UL configuration of the COT and may correspond to all ofthe GC-PDCCH transmission timings and all of the GC-PDCCH monitoringoccasions. In any of the GC-PDCCH transmission timings and the GC-PDCCHmonitoring occasions within the COT, the SFI-index fields of theGC-PDCCHs may indicate the same SFI combination which consists of SFI #0for slot 1 (i.e. the initial partial slot), SFI #0 for slots 2, 3, 4 and5, SFI #28 for slot 6, and SFI #1 for slots 7 and 8. In addition, theGC-PDCCH may also have a bit field to indicate additional information,where the additional information may change depending on the GC-PDCCHtransmission timings and the GC-PDCCH monitoring occasions. For example,the additional information may indicate a location of a certain slot(preferably the starting slot, but it works with another type of slot,e.g. the ending slot or the slot where the GC-PDCCH is detected) of theslots of which the SFIs are indicated by the detected GC-PDCCH whichalso carries the information concerned. The location may be a relativelocation (also referred to as a slot offset or a time-domain shift witha unit of slot) from (or to) the slot where the GC-PDCCH carrying theconcerned information is detected. The starting slot indicated by theconcerned information may also be the slot which the current COT startswith. Alternatively, the starting slot indicated by the concernedinformation may not always be the same as the slot which the current COTstarts with. Additionally and/or alternatively, the location may be alocation within a radio frame where the GC-PDCCH carrying the concernedinformation is detected, and the additional information may indicate aslot index of the starting slot within a radio frame.

This scheme may also apply to the wideband operation. The CG-PDCCH mayinclude a single SFI-index field, and the value of the SFI-index fieldmay apply to multiple LBT sub-bands. Additionally and/or alternatively,the CG-PDCCH may include a multiple SFI-index fields, and the value ofeach SFI-index field may apply to a respective LBT sub-band. TheCG-PDCCH may include a single bit field for indicating the COT startingtiming, and the value of the bit field may apply to multiple LBTsub-bands. Additionally and/or alternatively, the CG-PDCCH may includemultiple bit fields for indicating the COT starting timing, and thevalue of each bit field may apply to a respective LBT sub-band. TheCG-PDCCH may include a single SFI-index field and multiple bit fieldsfor indicating the COT starting timing. Alternatively, The CG-PDCCH mayinclude multiple SFI-index fields and a single bit field for indicatingthe COT starting timings.

Another aspect for enhancing of dynamic SFI signaling is COT length(also referred to as channel occupancy duration length) indication.There are several options that have been proposed in terms ofnotification of ‘COT end’ or ‘Out of COT’ indication. Option 1 is tosupport a new bit field for indicating COT ending position in the DCIformat (e.g. DCI format 2_0) which also include a bit field forindicating SFI. Option 2 is to define new slot formats in whichindicating a ‘COT end’ symbol or ‘Out of COT’ symbols, where the newslot formats may be included on the reserved entries in Table 1, similarto the addition of the Table 2 entries into Table 1. Option 3 is not tohave an explicit indication of COT end position but filling Flexiblesymbols in out-of-COT portion, instead.

Table 3 shows basic behaviors in a serving cell (i.e. non-NR-U cell) ina license band (e.g. a particular NR band such as NR band #N46). The UE102 may perform the basic behaviors for a given symbol depending on whatis configured or indicated for the symbol. The gNB 160 may assume thatUE 102 performs the basic behaviors for the symbol. In NR-U cell (i.e.in a serving cell in a license band), some UE behaviors may be differentfrom the ones shown in Table 3. For example, behaviors of UE 102configured with dynamic SFI monitoring but not detecting the dynamic SFIare defined separately from the behaviors of UE 102 not configured withdynamic SFI monitoring. For the case of Flexible bytdd-UL-DL-configuration (i.e. tdd-UL-DL-configuration-Common and/ortdd-UL-DL-configuration-Dedicated if provided), the UE behavior shouldbe different from the one in Table 3, because semi-persistent orperiodic DL transmission is not always possible due to LBT. Morespecifically, in Flexible by tdd-UL-DL-configuration the UE should notperform semi-persistent or periodic DL reception.

PDCCH monitoring may be a monitoring of PDCCH with DCI formats which CRCscrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s). Thesemi-persistent or periodic DL reception may be PDSCH reception andCSI-RS reception which are configured by higher layers (e.g. RRC layer).The semi-persistent or periodic DL reception may be PDSCH reception andCSI-RS reception which are configured by higher layers (e.g. RRC layer),for example reception of configured scheduling based PDSCH (alsoreferred to as semi-persistent-scheduling (SPS) PDSCH), reception ofperiodic CSI-RS, etc. The semi-persistent or periodic UL transmissionmay be PUCCH, or PUSCH, or PRACH transmission and SRS transmission whichare configured by higher layers (e.g. RRC layer), for example periodicCSI reporting on PUCCH, configured scheduling based PUSCH transmission,periodic SRS transmission etc. It is noted that configuration by higherlayers may require processing to send and/or to acquire higher layerinformation (e.g. RRC information carried in RRC message, MACinformation carried in MAC CE) in the higher layer.

In NR-U cell, some of the UE behaviors may need to be changed. Forexample, for the symbols indicated as Flexible bytdd-UL-DL-configuration and if the dynamic SFI is not configured ordynamic SFI indicates slot format index 255, the PDCCH monitoring (alsoreferred to as regular PDCCH monitoring) may be performed based on theshorter periodicity, compared to the one (i.e. regular periodicity) usedfor PDCCH monitoring on the symbols indicated as DL bytdd-UL-DL-configuration.

TABLE 3 Basic behaviors. What is Semi-persistent Semi-persistentDynamically Dynamically indicated/configured PDCCH or periodic DL orperiodic UL scheduled DL scheduled UL for the symbol(s) monitoringreception transmission reception transmission DL by tdd-UL-DL-Performed. Performed. Not Performed. Not configuration performed.expected. (irrespective of whether/how to be indicated by dynamic SFI)UL by tdd-UL-DL- Not Not Performed. Not Performed. configurationperformed. performed. expected. (irrespective whether/how to beindicated by dynamic SFI) Flexible by tdd- Performed, Performed,Performed, Performed. Performed. UL-DL-configuration unless unlessunless (dynamic SFI is not overridden by overridden by cancelled byconfigured or dynamically dynamically dynamically dynamic SFI scheduledUL scheduled UL scheduled DL indicates 255) transmission transmissionreception Flexible by tdd- Performed, Not Not Performed. Performed.UL-DL-configuration unless performed. performed. (dynamic SFI isoverridden by configured but not dynamically detected) scheduled ULtransmission DL by dynamic SFI Performed. Performed. Not Performed. Notperformed. expected. UL by dynamic SFI Not Not Performed. Not Performed.performed. performed. expected. Flexible by dynamic Not Not NotPerformed. Performed. SFI performed. performed. performed.ssb-PositionsInBurst — — Not — Not performed. performed. Valid PRACH NotNot — Not — occasions and gaps receiving performed. performed. PDCCH forType-1 CSS set.

A PDCCH with a particular DCI format (also referred to as GC-PDCCH) maybe transmitted in a common search space set. The DCI format (e.g. DCIformat 2_0 or DCI format 2_4) for GC-PDCCH may be used for notifying theslot format. Slot format indicator 1, Slot format indicator 2, . . . ,Slot format indicator N_(SFI) may be transmitted by means of the DCIformat. Additionally and/or alternatively Channel Occupancy indicator 1,Channel Occupancy indicator 2, . . . , Channel Occupancy indicatorN_(COI) may be transmitted by means of the DCI format. The UE 102 may beprovided RRC information (RRC parameter(s)) indicating a location of aChannel Occupancy indicator index (COI-index) field in the DCI format bypositionInDCI. Additionally and/or alternatively Available RB-Rangeindicator 1, Available RB-Range indicator 2, . . . , Available RB-Rangeindicator N_(RB_Range) may be transmitted by means of the DCI format.The UE 102 may be provided RRC information (RRC parameter(s)) indicatinga location of a Available RB-Range indicator index (RB-Range-index)field in the DCI format by positionInDCI. The DCI format may be with CRCscrambled by SFI-RNTI. Alternatively, the DCI format may be with CRCscrambled by another such as channel occupancy indicator-RNTI(COI-RNTI). The size of the DCI format may be configurable by higherlayers (e.g. RRC layer) up to 128 bits.

FIG. 29 shows an example of signaling of slot format and COT structure.This example may be related to Option 1. GC-PDCCH may be transmitted bythe gNB 160 and may be monitored by the UE 102. The DCI format mayinclude SFI-index for indicating one of slot format combinations, andthe indicated slot format combination may indicate slot formats of oneor more slots. The DCI format may also include COI-index for indicatinga position of the end of channel occupancy. The end position may beidentified as the number of symbols from the starting symbol of thestarting slot of which the slot format is signaled by the same DCIformat. The duration from the starting symbol of the starting slot ofwhich the slot format is signaled to the symbol indicated as the endposition of channel occupancy may be recognized as the channel occupancytime (COT) initiated by a channel access at the gNB 160. The bit size ofeach COI-index field may be configurable. Alternatively, the bit size ofeach COI-index field may be fixed (e.g. 9 bits). The figure shows fivephases, Phase 0 to Phase 4.

Phase 0 may be considered to be one or more symbols for which the slotformat is not detected by the UE 102 and which are outside of COT (i.e.COI-index field value explicitly indicates the symbol(s) are not insideof COT or the GC-PDCCH providing the COI-index field value indicatingthat the symbol(s) is inside of COT is not detected). Phase 0 may beconsidered to be one or more symbols for which the slot format is nottransmitted by the gNB 160 and which are outside of COT (i.e. COI-indexfield value explicitly indicates the symbol(s) are not inside of COT orthe GC-PDCCH providing the COI-index field value indicating that thesymbol(s) is inside of COT is not transmitted).

Phase 1 may be considered to be one or more symbols which are indicatedas downlink by the GC-PDCCH detected by the UE 102 and which areindicates as inside of COT. Phase 1 may be considered to be one or moresymbols which are indicated as downlink by the GC-PDCCH transmitted bythe gNB 160 and which are indicates as inside of COT.

Phase 2 may be considered to be one or more symbols which are indicatedas Flexible by the GC-PDCCH detected by the UE 102 and which areindicates as inside of COT. Phase 2 may be considered to be one or moresymbols which are indicated as Flexible by the GC-PDCCH transmitted bythe gNB 160 and which are indicates as inside of COT.

Phase 3 may be considered to be one or more symbols which are indicatedas uplink by the GC-PDCCH detected by the UE 102 and which are indicatesas inside of COT. Phase 3 may be considered to be one or more symbolswhich are indicated as uplink by the GC-PDCCH transmitted by the gNB 160and which are indicates as inside of COT.

Phase 4 may be considered to be one or more symbols which are indicatedas either downlink, uplink or Flexible by the GC-PDCCH detected by theUE 102 and which are indicates as outside of COT. Phase 4 may beconsidered to be one or more symbols which are indicated as eitherdownlink, uplink or Flexible by the GC-PDCCH transmitted by the gNB 160and which are indicates as outside of COT.

FIG. 30 shows an example of signaling of slot format and COT structure.This example may be related to Option 1. The figure shows three phases,Phase 0, Phase 1 and Phase 5. Phase 0 and Phase 1 may be the same as theaforementioned Phase 0 and Phase 1, respectively.

Phase 5 may be considered to be one or more symbols for which the slotformat is not detected by the UE 102 and which are inside of COT (i.e.GC-PDCCH providing the COI-index field value indicating that thesymbol(s) is inside of COT is detected). Phase 5 may be considered to beone or more symbols for which the slot format is not transmitted by thegNB 160 and which are inside of COT (i.e. GC-PDCCH providing theCOI-index field value indicating that the symbol(s) is inside of COT istransmitted). The slot format for symbols during Phase 5 may beindicated by another GC-PDCCH later on. When indicated, Phase 5 maychange to either Phase 1, Phase 2, Phase 3 or a combination of them. TheUE 102 may not expect that symbols in Phase 5 would be indicated asoutside of COT by the later GC-PDCCH.

FIG. 31 shows an example of signaling of slot format and COT structure.This example may be related to Option 2. The DCI format may includeSFI-index for indicating one of slot format combinations, and theindicated slot format combination may indicate slot formats of one ormore slots. The DCI format may not include COI-index for indicating aposition of the end of channel occupancy. The end position may beindicated by the slot format. For example, a slot format where a singlesymbol is set to ‘COT end’ value may be defined. If the slot formatcombination indicated by SFI-index includes such slot format, the symbolset to ‘COT end’ may be considered as the end position of the COT. Thesymbols later than the symbol set to ‘COT end’ may be set to Flexible,but those symbols may be considered to be indicated as outside of COT.For example, a slot format where symbol(s) in the last part of the slotare set to ‘Out of COT’ value may be defined. The duration from thestarting symbol of the starting slot of which the slot format issignaled to the last symbol indicated as either downlink, uplink orFlexible (i.e. other than ‘Out of COT’ value) may be recognized as thechannel occupancy time (COT) initiated by a channel access at the gNB160. The figure shows five phases, Phase 0 to Phase 4, which may bebasically the same as the aforementioned Phase 0 and Phase 4,respectively. Phase 0 may be considered to be one or more symbols forwhich the slot format is not detected by the UE 102. Phase 0 may beconsidered to be one or more symbols for which the slot format is nottransmitted by the gNB 160. Phase 4 may be considered to be one or moresymbols which are indicated as outside of COT by the GC-PDCCH detectedby the UE 102. Phase 4 may be considered to be one or more symbols whichare indicated as outside of COT by the GC-PDCCH transmitted by the gNB160. In this example, Phase 4 may be shorter than a slot length.

FIG. 32 shows an example of signaling of slot format and COT structure.This example may be related to Option 2 and Option 3. The figure showstwo phases, Phase 0 and Phase 1. Phase 0 and Phase 1 may be basicallythe same as the aforementioned Phase 0 and Phase 1, respectively. Phase0 may be considered to be one or more symbols for which the slot formatis not detected by the UE 102. Phase 0 may be considered to be one ormore symbols for which the slot format is not transmitted by the gNB160.

FIG. 33 shows an example of signaling of slot format and COT structure.This example may be related to Option 3. The figure shows four phases,Phase 0 and Phase 3. Phase 0 and Phase 3 may be basically the same asthe aforementioned Phase 0 and Phase 3, respectively.

With any option, UE behaviors in Phase 0 may need to be defined. To besafer, the UE 102 should consider Phase 0 duration as out of the gNB'sCOT. Regarding PDCCH monitoring, PDCCH monitoring with finer granularity(e.g. PDCCH monitoring with a different periodicity from a regularperiodicity where both periodicities may be configured by RRC signalingindividually) may be performed in Phase 0. Once the gNB acquire achannel access for a PDCCH transmission by using Cat-4 LBT, thefollowing PDSCH can also be transmitted. Hence, the dynamicallyscheduled DL reception may be assumed to be performed, too. Even outsideof the gNB's COT, uplink transmission subject to Cat-4 LBT may beallowed. Therefore, both the semi-persistent or periodic UL transmissionand the dynamically scheduled UL transmission may be done in Phase 0. Onthe other hand, the UE may not assume the presence of semi-persistent orperiodic DL signals, as the DL transmission is subject to LBT. Ifdynamic SFI is configured (i.e. RRC parameters for monitoring of PDCCHwith the DCI format including SFI-index field is provided) but dynamicSFI (GC-PDCCH with the DCI format including the SFI-index field) for agiven symbol(s) is not detected, UE behavior on the symbol(s) is one, asub-set or all of the following: (1) the UE performs PDCCH monitoringwith finer granularity if configured (regular periodicity may be usedotherwise), (2) the UE does not perform other semi-persistent orperiodic DL reception, (3) the UE performs semi-persistent or periodicUL transmission subject to LBT, (4) the UE performs dynamicallyscheduled DL reception, and (5) the UE performs dynamically scheduled ULtransmission subject to LBT.

In Option 1, Phase 1, 2 and 3 can follow the UE behaviors in Table 3,i.e. “DL by dynamic SFI”, “UL by dynamic SFI”, and “Flexible by dynamicSFI” in Table 3, respectively.

Although Phase 4 is explicitly indicated as outside of COT, the UEbehavior can follow the one for out of COT and therefore the UE behaviorin Phase 4 may be the same as in Phase 0. More specifically, for eitherDL or Flexible by tdd-UL-DL-configuration and if a parameter forGC-PDCCH monitoring is provided and if the DCI format indicating the setof symbols as outside of the channel occupancy is detected, the regularPDCCH monitoring may be performed based on shorter periodicity (alsoreferred to as finer granularity, e.g. a periodicity different from aregular periodicity such as slot-wise periodicity). Semi-persistent orperiodic DL reception may not be performed. Dynamically scheduled DLreception may be performed if scheduled. For UL bytdd-UL-DL-configuration and if a parameter for GC-PDCCH monitoring isprovided and if the DCI format indicating the set of symbols as outsideof the channel occupancy is detected, semi-persistent or periodic ULtransmission may be performed and dynamically scheduled UL transmissionmay be performed if scheduled. Neither PDCCH monitoring, semi-persistentor periodic DL reception nor dynamically scheduled DL reception may beperformed.

Phase 5 is explicitly indicated as inside of COT but has not beenindicated with any particular slot format. Slot format for Phase 5 maybe able to be indicated by a later dynamic SFI. The UE behavior forFlexible by tdd-UL-DL-configuration (dynamic SFI is not configured ordynamic SFI indicates 255) can be reused in Phase 5. More specifically,for either DL or Flexible by tdd-UL-DL-configuration and if a parameterfor GC-PDCCH monitoring is provided and if the DCI format providing aslot format for the slot is not detected and if the DCI formatindicating the set of symbols in the slot as inside of channel occupancyis detected, the regular PDCCH monitoring may be performed on the set ofsymbols in the slot based on the shorter periodicity. Semi-persistent orperiodic DL reception may be performed, unless overridden by dynamicallyscheduled UL transmission. Dynamically scheduled DL reception may beperformed if scheduled. For UL by tdd-UL-DL-configuration and if aparameter for GC-PDCCH monitoring is provided and if the DCI formatindicating the set of symbols as outside of the channel occupancy isdetected, semi-persistent or periodic UL transmission may be performedand dynamically scheduled UL transmission may be performed if scheduled.Neither PDCCH monitoring, semi-persistent or periodic DL reception nordynamically scheduled DL reception may be performed.

In Option 2, Phase 1, 2 and 3 can follow the UE behaviors in Table 3.There may be no difference between Option 1 Phase 4 and Option 2 Phase 4in terms of UE's knowledge, though signaling mechanisms are differentbetween Options 1 and 2. Therefore, UE behavior in Phases 4 in Option 2can be the same as for Phase 4 in Option 1. Compared with Option 1,Option 2 does not have Phase 5, as the UE cannot distinguish them. Fromthe UE behavior point of view, the only difference between Phases 0 and5 may be PDCCH monitoring granularity, namely Phase 0 requires finergranularity while regular granularity is used in Phase 5. However, if alater dynamic SFI indicates slot formats for the remaining inside-COTduration, such finer PDCCH monitoring may not be required.

In Option 3, Phase 1, 2 and 3 can follow the UE behaviors in Table 3.The difference from Option 2 is semi-persistent or periodic DL receptionand UL transmission are prohibited in the Flexible symbols indicated bydynamic SFI.

Channel access procedures for UL transmissions are described. A channelmay refer to a carrier or a part of a carrier consisting of a contiguousset of resource blocks (RBs) on which a channel access procedure isperformed in shared spectrum. A channel access procedure may be aprocedure based on sensing that evaluates the availability of a channelfor performing transmissions. The basic unit for sensing is a sensingslot with a duration T_(sl)=9 us. The sensing slot duration T_(sl) isconsidered to be idle if an eNB/gNB or a UE senses the channel duringthe sensing slot duration, and determines that the detected power for atleast 4 us within the sensing slot duration is less than energydetection threshold X_(Thresh). Otherwise, the sensing slot durationT_(sl) is considered to be busy. A channel occupancy may refer totransmission(s) (including DL transmission(s) and UL transmission(s)) onchannel(s) by eNB/gNB/UE(s) after performing the corresponding channelaccess procedures. A Channel Occupancy Time may refer to the total timefor which eNB/gNB/UE and any eNB/gNB/UE(s) sharing the channel occupancyperform transmission(s) on a channel after an eNB/gNB/UE performs thecorresponding channel access procedures described in this clause. Fordetermining a Channel Occupancy Time, if a transmission gap is less thanor equal to 25 us, the gap duration is counted in the channel occupancytime. A channel occupancy time can be shared for transmission between aneNB/gNB and the corresponding UE(s). A DL transmission burst may bedefined as a set of transmissions from an eNB/gNB without any gapsgreater than 16 us. Transmissions from an eNB/gNB separated by a gap ofmore than 16 us are considered as separate DL transmission bursts. AneNB/gNB can transmit transmission(s) after a gap within a DLtransmission burst without sensing the corresponding channel(s) foravailability. A UL transmission burst may be defined as a set oftransmissions from a UE without any gaps greater than 16 us.Transmissions from a UE separated by a gap of more than 16 us areconsidered as separate UL transmission bursts. A UE can transmittransmission(s) after a gap within a UL transmission burst withoutsensing the corresponding channel(s) for availability.

A UE can access a channel on which UL transmission(s) are performedaccording to one of aforementioned Type 1 or Type 2 UL channel accessprocedures.

If a UL grant scheduling a PUSCH transmission indicates Type 1 channelaccess procedures, the UE may have to use Type 1 channel accessprocedures for transmitting transmissions including the PUSCHtransmission unless stated otherwise.

A UE may have to use Type 1 channel access procedures for transmittingtransmissions including the autonomous or configured grant PUSCHtransmission on configured UL resources unless stated otherwise.

If a UL grant scheduling a PUSCH transmission indicates Type 2 channelaccess procedures, the UE may have to use Type 2 channel accessprocedures for transmitting transmissions including the PUSCHtransmission unless stated otherwise.

A UE may have to use Type 1 channel access procedures for transmittingSRS transmissions not including a PUSCH transmission. UL channel accesspriority class P=1 in FIG. 18 is used for SRS transmissions notincluding a PUSCH.

If a UE is scheduled by an eNB/gNB to transmit PUSCH and SRS incontiguous transmissions without any gaps in between, and if the UEcannot access the channel for PUSCH transmission, the UE may have toattempt to make SRS transmission according to uplink channel accessprocedures specified for SRS transmission.

A single DCI format (e.g. DCI format 0_1 (i.e. a UL grant) and DCIformat 1_1 (i.e. a DL grant)) may schedule a UL transmission and mayalso trigger a SRS transmission where there is a gap (longer than 16microseconds) between the UL transmission and the SRS transmission. TheDCI format may include a single ChannelAccess-CPext-CAPC field forindicating a combination of a channel access type, a CP extension indexand a channel access priority class. In this case, the first one of thetwo non-consecutive UL transmissions scheduled with the single DCIfollows the CP extension and the LBT type (i.e. Type 1 or Type 2 ULchannel access procedure) indicated by the information field in the DCIformat, regardless of whether it is SRS or PUSCH/PUCCH. The second oneof the two non-consecutive UL transmissions scheduled with the singleDCI may not follow the CP extension and the LBT type but may usezero-long CP extension and Type 1 UL channel access procedure unlessswitched to Type 2 UL channel access procedure, regardless of whether itis SRS or PUSCH/PUCCH. On the other hand, the channel access priorityclass indicated by the information field in the DCI format may apply toPUSCH or PUCCH transmissions, regardless if whether it is the first orsecond transmission. Moreover, UL channel access priority class P=1 inFIG. 18 may apply to the SRS transmission, regardless of whether it isthe first or second transmission.

If a UE is scheduled by a gNB with a UL grant indicating Type 1 channelaccess procedures to transmit PUSCH and SRS in transmissions with a gapin between, and if the PUSCH transmission is earlier than the SRStransmission, the UE may have to use the Type 1 channel accessprocedures and the UL channel access priority class indicated by the ULgrant for the PUSCH transmission, and the Type 1 channel accessprocedure and UL channel access priority class p=1 in FIG. 18 for theSRS transmission. If the SRS transmission is earlier than the PUSCHtransmission, the UE may have to use the Type 1 channel accessprocedures and UL channel access priority class p=1 in FIG. 18 for theSRS transmission, and the Type 1 channel access procedures and the ULchannel access priority class indicated by the UL grant for the PUSCHtransmission.

If a UE is scheduled by a gNB with a UL grant indicating Type 2 channelaccess procedures to transmit PUSCH and SRS in transmissions with a gapin between, and if the PUSCH transmission is earlier than the SRStransmission, the UE may have to use the Type 2 channel accessprocedures for the PUSCH transmission and the Type 1 channel accessprocedure and UL channel access priority class P=1 in FIG. 18 for theSRS transmission. If the SRS transmission is earlier than the PUSCHtransmission, the UE may have to use the Type 2 channel accessprocedures and UL channel access priority class p=1 in FIG. 18 for theSRS transmission and the Type 1 channel access procedures and the ULchannel access priority class indicated by the UL grant for the PUSCHtransmission.

A UE may have to use Type 1 channel access procedures for PUCCHtransmissions unless stated otherwise in this clause. If a DL grant or arandom access response (RAR) message for successRAR scheduling a PUCCHtransmission indicates Type 2 channel access procedures, the UE may haveto use Type 2 channel access procedures.

When a UE uses Type 1 channel access procedures for PUCCH transmissionsor PUSCH only transmissions without UL-SCH, the UE may have to use ULchannel access priority class P=1 in FIG. 18 .

If a UE is scheduled by a gNB with a DL grant indicating Type 1 channelaccess procedures to transmit PUCCH and SRS in transmissions with a gapin between, and if the PUCCH transmission is earlier than the SRStransmission, the UE may have to use the Type 1 channel accessprocedures for the PUCCH transmission, and the Type 1 channel accessprocedure and UL channel access priority class P=1 in FIG. 18 for theSRS transmission. If the SRS transmission is earlier than the PUCCHtransmission, the UE may have to use the Type 1 channel accessprocedures and UL channel access priority class P=1 in FIG. 18 for theSRS transmission, and the Type 1 channel access procedures for the PUCCHtransmission.

If a UE is scheduled by a gNB with a DL grant indicating Type 2 channelaccess procedures to transmit PUCCH and SRS in transmissions with a gapin between, and if the PUCCH transmission is earlier than the SRStransmission, the UE may have to use the Type 2 channel accessprocedures for the PUCCH transmission, and the Type 1 channel accessprocedure and UL channel access priority class P=1 in FIG. 18 for theSRS transmission. If the SRS transmission is earlier than the PUCCHtransmission, the UE shall use the Type 2 channel access procedures andUL channel access priority class p=1 in FIG. 18 for the SRStransmission, and the Type 1 channel access procedures for the PUCCHtransmission.

A UE may have to use Type 1 channel access procedure for PRACHtransmissions and PUSCH transmissions without user plane data related torandom access procedure that initiate a channel occupancy with ULchannel access priority class p=1 in FIG. 18 .

When a UE uses Type 1 channel access procedures for PUSCH transmissionson configured resource, the UE may determine the corresponding ULchannel access priority p in FIG. 18 .

When a UE uses Type 1 channel access procedures for PUSCH transmissionswith user plane data indicated by a UL grant or related to random accessprocedure where the corresponding UL channel access priority p is notindicated, the UE may determine p in FIG. 18 following the sameprocedures as for PUSCH transmission on configured resources using Type1 channel access procedures.

When a UE uses Type 2A, Type 2B, or Type 2C UL channel access proceduresfor PUSCH transmissions indicated by a UL grant or related to randomaccess procedures where the corresponding UL channel access priority pis not indicated, the UE may assume that the channel access priorityclass p=4 is used by the gNB for the Channel Occupancy Time.

A UE may not transmit on a channel for a Channel Occupancy Time thatexceeds T_(ulm,cot,p) where the channel access procedure is performedbased on the channel access priority class P associated with the UEtransmissions, as given in FIG. 18 .

The total Channel Occupancy Time of autonomous uplink transmission(s)obtained by the channel access procedure in this clause, including thefollowing DL transmission if the UE sets ‘COT sharing indication’ inAUL-UCI to ‘1’ in a subframe within the autonomous uplinktransmission(s), may not exceed T_(ulm cot,p), where T_(ulm cot,p) isgiven in FIG. 18 .

If a UE determines the duration in time domain and the location infrequency domain of a remaining channel occupancy initiated by the gNBfrom a DCI format 2_0 as described in the DCI format 2_0 relatedprocedures, the UE may switch from Type 1 channel access procedures toType 2A channel access procedures for its corresponding UL transmissionswithin the determined duration in time and location in frequency domainof the remaining channel occupancy. In this case, if the ULtransmissions are PUSCH transmissions on configured resources, the UEmay assume any priority class for the channel occupancy shared with thegNB.

An example of DCI format 2_0 related procedure is described. Thefollowing may apply for a serving cell that is included in a set ofserving cells configured to a UE 102 by RRC parametersslotFormatCombToAddModList and slotFormatCombToReleaseList,availableRB-SetsToAddModList-r16 and availableRB-SetsToRelease-r16,search Space SwitchTriggerToAddModList-r16 and search SpaceSwitchTriggerToReleaseList-r16, or co-DurationsPerCell ToAddModList-r16and co-DurationsPerCellToReleaseList-r16.

If a UE 102 is configured by higher layers with RRC parameterSlotFormatIndicator, the UE 102 may be provided a SFI-RNTI by RRCparameter sfi-RNTI and with a payload size of DCI format 2_0 by RRCparameter dci-PayloadSize.

The UE 102 may also be provided in one or more serving cells with aconfiguration for a search space set s and a corresponding CORESET p formonitoring M_(p,s) ^((L) ^(SFI) ⁾ PDCCH candidates for DCI format 2_0with a CCE aggregation level of L_(SFI) CCEs. The M_(p,s) ^((L) ^(SFI) ⁾PDCCH candidates are the first M_(p,s) ^((L) ^(SFI) ⁾ PDCCH candidatesfor CCE aggregation level L_(SFI) for search space set s in CORESET p.

For each serving cell in the set of serving cells, the UE 102 can beprovided the following 8 parameters.

(1) An identity of the serving cell by RRC parameter servingCellId maybe provided.

(2) A location of a SFI-index field in DCI format 2_0 by RRC parameterpositionInDCI may be provided.

(3) A set of slot format combinations by RRC parameterslotFormatCombinations, where each slot format combination in the set ofslot format combinations includes (3-a) One or more slot formatsindicated by a respective RRC parameter slotFormats for the slot formatcombination and (3-b) a mapping for the slot format combination providedby RRC parameter slotFormats to a corresponding SFI-index field value inDCI format 2_0 provided by RRC parameter slotFormatCombinationId, may beprovided.

(4) For unpaired spectrum operation, a reference SCS configurationμ_(SFI) by RRC parameter subcarrierSpacing and, when a supplementary ULcarrier is configured for the serving cell, a reference SCSconfiguration μ_(SFI,SUL) by RRC parameter subcarrierSpacing2 for thesupplementary UL carrier may be provided.

(5) For paired spectrum operation, a reference SCS configurationμ_(SFI,DL) for a DL BWP by RRC parameter subcarrierSpacing and areference SCS configuration μ_(SFI,UL) for an UL BWP by RRC parametersubcarrierSpacing2 may be provided.

(6) A location of a RB set indicator field in DCI format 2_0 that is oneof (6-a) and (6-b).

(6-a) One bit, if intraCellGuardBandDL-r16 for the serving cellindicates no intra-cell guard-bands are configured, where a value of ‘1’indicates that the serving cell is available for receptions, a value of‘0’ indicates that the serving cell is not available for receptions, byavailableRB-SetPerCell-r16, and the serving cell remains available orunavailable for reception until the end of the indicated channeloccupancy duration

(6-b) a bitmap having a one-to-one mapping with the RB sets of theserving cell, if intraCellGuardBandDL-r16 for the serving cell indicatesintra-cell guard-bands are configured, where the bitmap includesN_(RB,set,DL) bits and N_(RB,set,DL) is the number of RB sets in theserving cell, a value of ‘1’ indicates that an RB set is available forreceptions, a value of ‘0’ indicates that an RB set is not available forreceptions, by availableRB-SetPerCell-r16 and a RB set remains availableor unavailable for receptions until the end of the indicated channeloccupancy duration.

(7) A location of a channel occupancy duration field in DCI format 2_0,by CO-DurationPerCell-r16, that indicates a remaining channel occupancyduration for the serving cell starting from a first symbol of a slotwhere the UE detects the DCI format 2_0 by providing a value fromCO-DurationList-r16. The channel occupancy duration field includesmax{┌log₂(COdurationListSize)┐1} bits, where COdurationListSize is thenumber of values provided by CO-DurationList-r16. IfCO-DurationPerCell-r16 is not provided, the remaining channel occupancyduration for the serving cell is a number of slots, starting from theslot where the UE detects the DCI format 2_0, that the SFI-index fieldvalue provides corresponding slot formats. For a set of symbols where achannel occupancy duration field in DCI format 2_0 indicates as notbeing within a remaining channel occupancy duration, the UE 102 mayperform procedures for outside of channel occupancy durations (e.g. (z1)to (z7) described below). A reference SCS configuration forCO-DurationList-r16, by subcarrierSpacing-r16 may also be provided,which may be used as a reference SCS to determine a unit of symbollength to indicate the CO duration.

(8) A location of a search space set group switching field in DCI format2_0 may be provided, by RRC parameter SearchSpaceSwitchTrigger-r16, thatindicates a group from two groups of search space sets for PDCCHmonitoring for scheduling on the serving cell.

A SFI-index field value in a DCI format 2_0 indicates to a UE 102 a slotformat for each slot in a number of slots for each DL BWP or each UL BWPstarting from a slot where the UE 102 detects the DCI format 2_0. Thenumber of slots is equal to or larger than a PDCCH monitoringperiodicity for DCI format 2_0. The SFI-index field includes max{┌log₂(maxSFIndex x+1)┐, 1} bits where maxSFIindex is the maximum valueof the values provided by corresponding RRC parameterslotFormatCombinationId. A slot format is identified by a correspondingformat index as provided in Table 1 where ‘D’ denotes a downlink symbol,‘U’ denotes an uplink symbol, and ‘F’ denotes a flexible symbol.

If a PDCCH monitoring periodicity for DCI format 2_0, provided to a UE102 for the search space set S by RRC parametermonitoringSlotPeriodicityAndOffset, is smaller than a duration of a slotformat combination the UE 102 obtains at a PDCCH monitoring occasion forDCI format 2_0 by a corresponding SFI-index field value, and the UE 102detects more than one DCI formats 2_0 indicating a slot format for aslot, the UE 102 expects each of the more than one DCI formats 2_0 toindicate a same format for the slot.

If a PDCCH monitoring periodicity for DCI format 2_0, provided to a UE102 for the search space set s by RRC parametermonitoringSlotPeriodicityAndOffset, is smaller than a duration of a slotformat combination the UE 102 obtains at a PDCCH monitoring occasion forDCI format 2_0 by a corresponding SFI-index field value, and the UE 102detects more than one DCI formats 2_0 indicating a slot format for aslot, the UE 102 expects each of the more than one DCI formats 2_0 toindicate a same format for the slot.

For unpaired spectrum operation for a UE 102 on a serving cell, the UE102 is provided by RRC parameter subcarrierSpacing a reference SCSconfiguration μ_(SFI) for each slot format in a combination of slotformats indicated by a SFI-index field value in DCI format 2_0. The UE102 expects that for a reference SCS configuration μ_(SFI) and for anactive DL BWP or an active UL BWP with SCS configuration μ, it isμ≥μ_(SFI). Each slot format in the combination of slot formats indicatedby the SFI-index field value in DCI format 2_0 is applicable to 2^((μ-μ)^(SFI) ⁾ consecutive slots in the active DL BWP or the active UL BWPwhere the first slot starts at a same time as a first slot for thereference SCS configuration μ_(SFI) and each downlink or flexible oruplink symbol for the reference SCS configuration μ_(SFI) corresponds to2^((μ-μ) ^(SFI) ⁾ consecutive downlink or flexible or uplink symbols forthe SCS configuration μ.

For paired spectrum operation for a UE 102 on a serving cell, theSFI-index field in DCI format 2_0 indicates a combination of slotformats that includes a combination of slot formats for a reference DLBWP and a combination of slot formats for a reference UL BWP of theserving cell. The UE 102 is provided by RRC parameter subcarrierSpacinga reference SCS configuration μ_(SFI,DL) for the combination of slotformats indicated by the SFI-index field value in DCI format 2_0 for thereference DL BWP of the serving cell. The UE 102 is provided bysubcarrierSpacing2 a reference SCS configuration μ_(SFI,UL) for thecombination of slot formats indicated by the SFI-index field value inDCI format 2_0 for the reference UL BWP of the serving cell. Ifμ_(SFI-DL)≥μ_(SFI,UL) and for each 2^((μ) ^(SFI,DL) ^(−μ) ^(SFI,UL) ⁾+1values provided by a value of RRC parameter slotFormats, where the valueof RRC parameter slotFormats is determined by a value of RRC parameterslotFormatCombinationId in RRC parameter slotFormatCombination and thevalue of RRC parameter slotFormatCombinationId is set by the value ofthe SFI-index field value in DCI format 2_0, the first 2^((μ) ^(SFI,DL)^(−μ) ^(SFI,UL) ⁾ values for the combination of slot formats areapplicable to the reference DL BWP and the next value is applicable tothe reference UL BWP. If μ_(SFI,DL)<ρ_(SFI,UL) and for each 2^((μ)^(SFI,UL) ^(−μ) ^(SFI,DL) ⁾+1 values provided by RRC parameterslotFormats, the first value for the combination of slot formats isapplicable to the reference DL BWP and the next 2^((μ) ^(SFI,UL) ^(−μ)^(SFI,DL) ⁾ values are applicable to the reference UL BWP.

For paired spectrum operation for a UE 102 on a serving cell, theSFI-index field in DCI format 20 indicates a combination of slot formatsthat includes a combination of slot formats for a reference DL BWP and acombination of slot formats for a reference UL BWP of the serving cell.The UE 102 is provided by RRC parameter subcarrierSpacing a referenceSCS configuration μ_(SFI,DL) for the combination of slot formatsindicated by the SFI-index field value in DCI format 2_0 for thereference DL BWP of the serving cell. The UE 102 is provided bysubcarrierSpacing2 a reference SCS configuration μ_(SFI,UL) for thecombination of slot formats indicated by the SFI-index field value inDCI format 2_0 for the reference UL BWP of the serving cell. Ifμ_(SFI,DL)≥μ_(SFI,UL) and for each 2^((μ) ^(SFI,DL) ^(−μ) ^(SFI,UL) ⁾+1values provided by a value of RRC parameter slotFormats, where the valueof RRC parameter slotFormats is determined by a value of RRC parameterslotFormatCombinationId in RRC parameter slotFormatCombination and thevalue of slotFormatCombinationId is set by the value of the SFI-indexfield value in DCI format 2_0, the first 2^((μ) ^(SFI,DL) ^(−μ)^(SFI,UL) ⁾ values for the combination of slot formats are applicable tothe reference DL BWP and the next value is applicable to the referenceUL BWP. If μ_(SFI,DL)<μ_(SFI,UL) and for each 2^((μ) ^(SFI,UL) ^(−μ)^(SFI,DL) ⁾+1 values provided by RRC parameter slotFormats, the firstvalue for the combination of slot formats is applicable to the referenceDL BWP and the next 2^((μ) ^(SFI,UL) ^(−μ) ^(SFI,DL) ⁾ values areapplicable to the reference UL BWP.

For unpaired spectrum operation with a second UL carrier for a UE 102 ona serving cell, the SFI-index field value in DCI format 2_0 indicates acombination of slot formats that includes a combination of slot formatsfor a reference first UL carrier of the serving cell and a combinationof slot formats for a reference second UL carrier of the serving cell.The UE 102 is provided by RRC parameter subcarrierSpacing a referenceSCS configuration μ_(SFI) for the combination of slot formats indicatedby the SFI-index field in DCI format 2_0 for the reference first ULcarrier of the serving cell. The UE 102 is provided by RRC parametersubcarrierSpacing2 a reference SCS configuration μ_(SFI,SUL) for thecombination of slot formats indicated by the SFI-index field value inDCI format 2_0 for the reference second UL carrier of the serving cell.For each 2^((μ) ^(SFI) ^(−μ) ^(SFI,SUL) ⁾+1 values of RRC parameterslotFormats, the first 2^((μ) ^(SFI) ^(−μ) ^(SFI,SUL) ⁾ values for thecombination of slot formats are applicable to the reference first ULcarrier and the next value is applicable to the reference second ULcarrier.

The UE 102 expects to be provided a reference SCS configurationμ_(SFI,SUL) so that for an active UL BWP in the second UL carrier withSCS configuration μ_(SUL), it is μ_(SUL)≥μ_(SFI,SUL). Each slot formatfor a combination of slot formats indicated by the SFI-index field inDCI format 2_0 for the reference first UL carrier is applicable to2^((μ−μ) ^(SFI) ⁾ consecutive slots for the active DL BWP and the activeUL BWP in the first UL carrier where the first slot starts at a sametime as a first slot in the reference first UL carrier. Each slot formatfor the combination of slot formats for the reference second UL carrieris applicable to 2^((μ) ^(SUL) ^(−μ) ^(SFI,SUL) ⁾ consecutive slots forthe active UL BWP in the second UL carrier where the first slot startsat a same time as a first slot in the reference second UL carrier.

If a BWP in the serving cell is configured with μ=2 and with extendedCP, the UE 102 expects μ_(SFI)=0, μ_(SFI)=0.1, or μ_(SFI)=2. A formatfor a slot with extended CP is determined from a format for a slot withnormal CP. A UE 102 determines an extended CP symbol to be adownlink/uplink/flexible symbol if the overlapping normal CP symbolsthat are downlink/uplink/flexible symbols, respectively. A UE 102determines an extended CP symbol to be a flexible symbol if one of theoverlapping normal CP symbols is flexible. A UE 102 determines anextended CP symbol to be a flexible symbol if the pair of theoverlapping normal CP symbols includes a downlink and an uplink symbol.

A reference SCS configuration μ_(SFI) or μ_(SFI,DL) or μ_(SFI,UL) orμ_(SFI,SUL) is either 0, or 1, or 2 for FR1 and is either 2 or 3 forFR2.

For a set of symbols of a slot, a UE 102 does not expect to detect a DCIformat 2_0 with an SFI-index field value indicating the set of symbolsof the slot as uplink and to detect a DCI format 1_0, a DCI format 1_1,or DCI format 0_1 indicating to the UE 102 to receive PDSCH or CSI-RS inthe set of symbols of the slot.

For a set of symbols of a slot, a UE 102 does not expect to detect a DCIformat 2_0 with an SFI-index field value indicating the set of symbolsin the slot as downlink and to detect a DCI format 0_0, DCI format 0_1,DCI format 1_0, DCI format 1_1, DCI format 2_3, or a RAR UL grantindicating to the UE 102 to transmit PUSCH, PUCCH, PRACH, or SRS in theset of symbols of the slot.

For a set of symbols of a slot and if a UE 102 is not provided alocation of a SFI-index field in DCI format 2_0 by RRC parameterpositionInDCI, the UE 102 may consider that the UE 102 has not detecteda DCI format 2_0 providing a slot format for the set of symbols if theset of symbols is indicated by the DCI format 2_0 as not being within aremaining channel occupancy duration by a channel occupancy durationfield.

For a set of symbols of a slot of which a slot format is indicated by aDCI format 2_0 and by an SFI-index field, a UE 102 may consider that theUE 102 has not detected a DCI format 2_0 providing the slot format forthe set of symbols if the set of symbols is indicated by the DCI format2_0 as not being within a remaining channel occupancy duration by achannel occupancy duration field. In other words, the UE 102 may performthe procedures (z1) to (z7) described below, for a set of symbolsindicated as not being within a remaining channel occupancy duration,irrespective of whether a slot format is indicated by a DCI format 2_0for the set of symbols.

For a set of symbols of a slot and if a UE 102 is not provided alocation of a SFI-index field in DCI format 2_0 by RRC parameterpositionInDCI, the UE 102 transmits or receives on the set of symbolsaccording to the procedure where the UE 102 is not configured with asearch space set for a detection of PDCCH with DCI format 2_0, if theset of symbols is indicated by the DCI format 2_0 as being within aremaining channel occupancy duration by a channel occupancy durationfield. In other words, the UE 102 may perform transmission and/orreception procedures by referring to downlink/uplink flexible bytdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated ifprovided, but not by referring to a slot format indicated by DCI format2_0, for a set of symbols indicated as being within a remaining channeloccupancy duration

For a set of symbols of a slot that are indicated by a DCI format 2_0 asbeing within a remaining channel occupancy duration either by a channeloccupancy duration field or by an SFI-index field, a UE 102 does notexpect to detect at a later time a DCI format 2_0 indicating, either bya channel occupancy duration field or by an SFI-index field, that anysymbol from the set of symbols is not within a remaining channeloccupancy duration.

For a set of symbols of a slot that are indicated as downlink/uplink byRRC parameter tdd-UL-DL-ConfigurationCommon, or RRC parametertdd-UL-DL-ConfigurationDedicated, the UE 102 does not expect to detect aDCI format 2_0 with an SFI-index field value indicating the set ofsymbols of the slot as uplink/downlink, respectively, or as flexible.

For a set of symbols of a slot corresponding to SS/PBCH blocks withindexes indicated to a UE 102 by ssb-PositionsInBurst in SIB1, or byssb-PositionsInBurst in ServingCellConfigCommon, the UE 102 does notexpect to detect a DCI format 2_0 with an SFI-index field valueindicating the set of symbols of the slot as uplink.

For a set of symbols of a slot corresponding to a valid PRACH occasionand N_(gap) symbols before the valid PRACH occasion, the UE 102 does notexpect to detect a DCI format 2_0 with an SFI-index field valueindicating the set of symbols of the slot as downlink.

For a set of symbols of a slot indicated to a UE 102 by pdcch-ConfigSIB1in MIB for a CORESET for Type0-PDCCH CSS set, the UE 102 does not expectto detect a DCI format 2_0 with an SFI-index field value indicating theset of symbols of the slot as uplink.

For a set of symbols of a slot indicated to a UE 102 as flexible by RRCparameter tdd-UL-DL-ConfigurationCommon and RRC parametertdd-UL-DL-ConfigurationDedicated if provided, or whentdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated arenot provided to the UE 102, and if the UE 102 detects a DCI format 2_0providing a format for the slot using a slot format value other than255, the following 11 procedures may be applied.

(x1) If one or more symbols from the set of symbols are symbols in aCORESET configured to the UE 102 for PDCCH monitoring, the UE 102receives PDCCH in the CORESET only if an SFI-index field value in DCIformat 2_0 indicates that the one or more symbols are downlink symbols.

(x2) If an SFI-index field value in DCI format 2_0 indicates the set ofsymbols of the slot as flexible and the UE 102 detects a DCI formatindicating to the UE 102 to receive PDSCH or CSI-RS in the set ofsymbols of the slot, the UE 102 receives PDSCH or CSI-RS in the set ofsymbols of the slot.

(x3) If an SFI-index field value in DCI format 2_0 indicates the set ofsymbols of the slot as flexible and the UE 102 detects a DCI format or aRAR UL grant indicating to the UE 102 to transmit PUSCH, PUCCH, PRACH,or SRS in the set of symbols of the slot the UE 102 transmits the PUSCH,PUCCH, PRACH, or SRS in the set of symbols of the slot.

(x4) If an SFI-index field value in DCI format 2_0 indicates the set ofsymbols of the slot as flexible, and the UE 102 does not detect a DCIformat indicating to the UE 102 to receive PDSCH or CSI-RS, or the UE102 does not detect a DCI format or a RAR UL grant indicating to the UE102 to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of theslot, the UE 102 does not transmit or receive in the set of symbols ofthe slot.

(x5) If the UE 102 is configured by higher layers to receive PDSCH orCSI-RS in the set of symbols of the slot, the UE 102 receives the PDSCHor the CSI-RS in the set of symbols of the slot only if an SFI-indexfield value in DCI format 2_0 indicates the set of symbols of the slotas downlink.

(x6) If the UE 102 is configured by higher layers to receive DL PRS inthe set of symbols of the slot, the UE 102 receives the DL PRS in theset of symbols of the slot only if an SFI-index field value in DCIformat 2_0 indicates the set of symbols of the slot as downlink orflexible.

(x7) If the UE 102 is configured by higher layers to transmit PUCCH, orPUSCH, or PRACH in the set of symbols of the slot, the UE 102 transmitsthe PUCCH, or the PUSCH, or the PRACH in the slot only if an SFI-indexfield value in DCI format 2_0 indicates the set of symbols of the slotas uplink.

(x8) If the UE 102 is configured by higher layers to transmit SRS in theset of symbols of the slot, the UE 102 transmits the SRS only in asubset of symbols from the set of symbols of the slot indicated asuplink symbols by an SFI-index field value in DCI format 2_0.

(x9) A UE 102 does not expect to detect an SFI-index field value in DCIformat 2_0 indicating the set of symbols of the slot as downlink andalso detect a DCI format or a RAR UL grant indicating to the UE 102 totransmit SRS, PUSCH, PUCCH, or PRACH, in one or more symbols from theset of symbols of the slot.

(x10) A UE 102 does not expect to detect an SFI-index field value in DCIformat 2_0 indicating the set of symbols of the slot as downlink orflexible if the set of symbols of the slot includes symbolscorresponding to any repetition of a PUSCH transmission activated by anUL Type 2 grant PDCCH.

(x11) A UE 102 does not expect to detect an SFI-index field value in DCIformat 2_0 indicating the set of symbols of the slot as uplink and alsodetect a DCI format indicating to the UE 102 to receive PDSCH or CSI-RSin one or more symbols from the set of symbols of the slot.

If a UE 102 is configured by higher layers to receive a CSI-RS or aPDSCH in a set of symbols of a slot and the UE 102 detects a DCI format2_0 with a slot format value other than 255 that indicates a slot formatwith a subset of symbols from the set of symbols as uplink or flexible,or the UE 102 detects a DCI format indicating to the UE 102 to transmitPUSCH, PUCCH, SRS, or PRACH in at least one symbol in the set of thesymbols, the UE 102 cancels the CSI-RS reception in the set of symbolsof the slot or cancels the PDSCH reception in the slot.

If a UE 102 is configured by higher layers to receive a DL PRS in a setof symbols of a slot and the UE 102 detects a DCI format 2_0 with a slotformat value other than 255 that indicates a slot format with a subsetof symbols from the set of symbols as uplink, or the UE 102 detects aDCI format indicating to the UE 102 to transmit PUSCH, PUCCH, SRS, orPRACH in at least one symbol in the set of the symbols, the UE 102cancels the DL PRS reception in the set of symbols of the slot.

If a UE 102 is configured by higher layers to transmit SRS, or PUCCH, orPUSCH, or PRACH in a set of symbols of a slot and the UE 102 detects aDCI format 20 with a slot format value other than 255 that indicates aslot format with a subset of symbols from the set of symbols as downlinkor flexible, or the UE 102 detects a DCI format indicating to the UE 102to receive CSI-RS or PDSCH in a subset of symbols from the set ofsymbols, then the following 2 procedures may be applied.

(y1) The UE 102 does not expect to cancel the transmission in symbolsfrom the set of symbols that occur, relative to a last symbol of aCORESET where the UE 102 detects the DCI format 2_0 or the DCI format,after a number of symbols that is smaller than the PUSCH preparationtime T_(proc,2) for the corresponding PUSCH processing capability [6, TS38.214] assuming d_(2,1)=1 and μ corresponds to the smallest SCSconfiguration between the SCS configuration of the PDCCH carrying theDCI format 2_0 or the DCI format and the SCS configuration of the SRS,PUCCH, PUSCH or μ_(r), where μ_(r) corresponds to the SCS configurationof the PRACH if it is 15 kHz or higher; otherwise μ_(r)=0.

(y2) The UE 102 cancels the PUCCH, or PUSCH, or PRACH transmission inremaining symbols from the set of symbols and cancels the SRStransmission in remaining symbols from the subset of symbols.

If a UE 102 is configured by higher layers to receive a CSI-RS ordetects a DCI format 0_1 indicating to the UE 102 to receive a CSI-RS inone or more RB sets and a set of symbols of a slot, and the UE 102detects a DCI format 2_0 with bitmap indicating that any RB set from theone or more RB sets is not available for reception, the UE 102 cancelsthe CSI-RS reception in the set of symbols of the slot.

A UE 102 assumes that flexible symbols in a CORESET configured to the UE102 for PDCCH monitoring are downlink symbols if the UE 102 does notdetect an SFI-index field value in DCI format 2_0 indicating the set ofsymbols of the slot as flexible or uplink and the UE 102 does not detecta DCI format indicating to the UE 102 to transmit SRS, PUSCH, PUCCH, orPRACH in the set of symbols.

For a set of symbols of a slot that are indicated as flexible bytdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated ifprovided, or when tdd-UL-DL-ConfigurationCommon, andtdd-UL-DL-ConfigurationDedicated are not provided to the UE 102, and ifthe UE 102 does not detect a DCI format 2_0 providing a slot format forthe set of symbols of the slot, the following 7 procedures may beapplied.

(z1) The UE 102 receives PDSCH or CSI-RS in the set of symbols of theslot if the UE 102 receives a corresponding indication by a DCI format.

(z2) The UE 102 transmits PUSCH, PUCCH, PRACH, or SRS in the set ofsymbols of the slot if the UE 102 receives a corresponding indication bya DCI format or a RAR UL grant.

(z3) The UE 102 receives PDCCH.

(z4) If the UE 102 is configured by higher layers to receive PDSCH inthe set of symbols of the slot, the UE 102 does not receive the PDSCH inthe set of symbols of the slot.

(z4a) If the UE is configured by higher layers to receive CSI-RS (i.e.RRC-configured CSI-RS) in the set of symbols of the slot, the UE doesnot receive (the UE cancels to receive) the CSI-RS in the set of symbolsof the slot (i.e. the UE considers the CSI-RS as not valid), except whenUE is provided CO-DurationPerCell-r16 and the set of symbols of the slotare within the indicated remaining channel occupancy duration.

(z5) If the UE 102 is configured by higher layers to receive DL PRS inthe set of symbols of the slot, the UE 102 receives the DL PRS.

(z6) If the UE 102 is configured by higher layers to transmit SRS, orPUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE102 is not provided EnableConfiguredUL-r16, the UE 102 may perform the(z6-1) and (z6-2).

(z6-1) The UE 102 does not transmit the PUCCH, or the PUSCH, or thePRACH in the slot and does not transmit the SRS in symbols from the setof symbols in the slot, if any, starting from a symbol that is afterPUSCH preparation time T_(proc,2) for the corresponding PUSCH timingcapability assuming d_(2,1)=1 after a last symbol of a CORESET where theUE 102 is configured to monitor PDCCH for DCI format 2_0 and μcorresponds to the smallest SCS configuration between the SCSconfiguration of the PDCCH carrying the DCI format 2_0 and the SCSconfiguration of the SRS, PUCCH, PUSCH or μ_(r), where μ_(r) correspondsto the SCS configuration of the PRACH if it is 15 kHz or higher;otherwise μ_(r)=0.

(z6-2) The UE 102 does not expect to cancel the transmission of the SRS,or the PUCCH, or the PUSCH, or the PRACH in symbols from the set ofsymbols in the slot, if any, starting before a symbol that is after thePUSCH preparation time T_(proc,2) for the corresponding PUSCH timingcapability assuming d_(2,1)=1 after a last symbol of a CORESET where theUE 102 is configured to monitor PDCCH for DCI format 2_0 and pcorresponds to the smallest SCS configuration between the SCSconfiguration of the PDCCH carrying the DCI format 2_0 and the SCSconfiguration of the SRS, PUCCH, PUSCH or μ_(r), where μ_(r) correspondsto the SCS configuration of the PRACH if it is 15 kHz or higher;otherwise μ_(r)=0.

(z7) If the UE 102 is configured by higher layers to transmit SRS, orPUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE102 is provided RRC parameter EnableConfiguredUL-r16, the UE 102 cantransmit the SRS, or PUCCH, or PUSCH, or PRACH, respectively.

For a set of symbols of a slot that are indicated as flexible bytdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated ifprovided, or when tdd-UL-DL-ConfigurationCommon, andtdd-UL-DL-ConfigurationDedicated are not provided to the UE 102, and ifthe UE 102 detects a DCI format 2_0 indicating the set of symbols of theslot in a RB set as not being available for reception, the following 7procedures may be applied.

(v1) The UE 102 is not expected to receive a DCI format indicating PDSCHor CSI-RS in the set of symbols of the slot.

(v2) The UE 102 transmits PUSCH, PUCCH, PRACH, or SRS in the set ofsymbols of the slot if the UE 102 receives a corresponding indication bya DCI format or a RAR UL grant.

(v3) The UE 102 does not receive PDCCH.

(v4) If the UE 102 is configured by higher layers to receive PDSCH inthe set of symbols of the slot, the UE 102 does not receive the PDSCH inthe set of symbols of the slot.

(v4a) If the UE is configured by higher layers to receive CSI-RS in theset of symbols of the slot, the UE does not receive the CSI-RS in theset of symbols of the slot, except when UE is providedCO-DurationPerCell-r16 and the set of symbols of the slot are within theindicated remaining channel occupancy duration.

(v5) If the UE 102 is configured by higher layers to receive DL PRS inthe set of symbols of the slot, the UE 102 does not receive the DL PRS.

(v6) If the UE 102 is configured by higher layers to transmit SRS, orPUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE102 is not provided EnabkConfiguredUL-r16, the UE 102 may perform the(z6-1) and (z6-2).

(v6-1) The UE 102 does not transmit the PUCCH, or the PUSCH, or thePRACH in the slot and does not transmit the SRS in symbols from the setof symbols in the slot, if any, starting from a symbol that is afterPUSCH preparation time T_(proc,2) for the corresponding PUSCH timingcapability assuming d_(2,1)=1 after a last symbol of a CORESET where theUE 102 is configured to monitor PDCCH for DCI format 2_0 and μcorresponds to the smallest SCS configuration between the SCSconfiguration of the PDCCH carrying the DCI format 2_0 and the SCSconfiguration of the SRS, PUCCH, PUSCH or μ_(r), where μ_(r) correspondsto the SCS configuration of the PRACH if it is 15 kHz or higher;otherwise μ_(r)=0.

(v6-2) The UE 102 does not expect to cancel the transmission of the SRS,or the PUCCH, or the PUSCH, or the PRACH in symbols from the set ofsymbols in the slot, if any, starting before a symbol that is after thePUSCH preparation time T_(proc,2) for the corresponding PUSCH timingcapability assuming d_(2,1)=1 after a last symbol of a CORESET where theUE 102 is configured to monitor PDCCH for DCI format 2_0 and correspondsto the smallest SCS configuration between the SCS configuration of thePDCCH carrying the DCI format 2_0 and the SCS configuration of the SRS,PUCCH, PUSCH or μ_(r), where μ_(r) corresponds to the SCS configurationof the PRACH if it is 15 kHz or higher; otherwise μ_(r)=0.

(v7) If the UE 102 is configured by higher layers to transmit SRS, orPUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE102 is provided RRC parameter EnableConfiguredUL-r16, the UE 102 cantransmit the SRS, or PUCCH, or PUSCH, or PRACH, respectively.

For unpaired spectrum operation for a UE 102 on a cell in a frequencyband of FR1, and when the scheduling restrictions due to RRMmeasurements are not applicable, if the UE 102 detects a DCI formatindicating to the UE 102 to transmit in a set of symbols, the UE 102 isnot required to perform RRM measurements based on a SS/PBCH block orCSI-RS reception on a different cell in the frequency band if theSS/PBCH block or CSI-RS reception includes at least one symbol from theset of symbols.

FIG. 34 shows an example of a method for a UE 102. The method maycomprise receiving a downlink control information (DCI) format includingan information field (Step S3401). The information field may indicate acombination of a channel access type, a cyclic prefix (CP) extensionindex and a channel access priority class (CAPC). The method may alsocomprise transmitting a sounding reference signal (SRS) and a physicaluplink shared channel (PUSCH) (Step S3402). The SRS and the PUSCH may bebased on the DCI format. There may be a gap between the SRS and thePUSCH. The gap may be longer than 16 microseconds. If the SRS istransmitted earlier than the PUSCH, the channel access type and the CPextension index corresponding to the indicated combination may apply tothe SRS, a predetermined channel access type and a predetermined CPextension length may apply to the PUSCH, a predetermined CAPC may applyto the SRS, and the CAPC corresponding to the indicated combination mayapply to the PUSCH.

FIG. 35 shows an example of a method for a gNB 160. The method maycomprise transmitting a downlink control information (DCI) formatincluding an information field (Step S3501). The information field mayindicate a combination of a channel access type, a cyclic prefix (CP)extension index and a channel access priority class (CAPC). The methodmay also comprise receiving a sounding reference signal (SRS) and aphysical uplink shared channel (PUSCH) (Step S3502). The SRS and thePUSCH may be based on the DCI format. There may be a gap between the SRSand the PUSCH. The gap may be longer than 16 microseconds. If the SRS isreceived earlier than the PUSCH, the channel access type and the CPextension index corresponding to the indicated combination may apply tothe SRS, a predetermined channel access type and a predetermined CPextension length may apply to the PUSCH, a predetermined CAPC may applyto the SRS, and the CAPC corresponding to the indicated combination mayapply to the PUSCH.

It should be noted that the above-described variables used as number ofpieces or indices may be considered to be non-negative integers.

It should be noted that a decision on whether a given channel and/ordata (including TB and CB) is successfully received or not may be doneby referring to Cyclic Redundancy Check (CRC) bits which is appended tothe given channel and/or data.

It should be noted that various modifications are possible within thescope of the present invention defined by claims, and embodiments thatare made by suitably combining technical means disclosed according tothe different embodiments are also included in the technical scope ofthe present invention.

It should be noted that basically the UE 102 and the gNB 160 may have toassume same procedures. For example, when the UE 102 follows a givenprocedure (e.g., the procedure described above), the gNB 160 may alsohave to assume that the UE 102 follows the procedure. Additionally, thegNB 160 may also have to perform the corresponding procedures.Similarly, when the gNB 160 follows a given procedure, the UE 102 mayalso have to assume that the gNB 160 follows the procedure.Additionally, the UE 102 may also have to perform the correspondingprocedures. The physical signals and/or channels that the UE 102receives may be transmitted by the gNB 160. The physical signals and/orchannels that the UE 102 transmits may be received by the gNB 160. Thehigher-layer signals and/or channels (e.g., dedicated RRC configurationmessages) that the UE 102 acquires may be sent by the gNB 160. Thehigher-layer signals and/or channels (e.g., dedicated RRC configurationmessages, MAC CE messages) that the UE 102 sends may be acquired by thegNB 160.

It should be noted that names of physical channels and/or signalsdescribed herein are examples.

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or a processor. The term“computer-readable medium,” as used herein, may denote a computer-and/or processor-readable medium that is non-transitory and tangible. Byway of example, and not limitation, a computer-readable orprocessor-readable medium may include RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic-storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer or processor. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray® disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein maybe implemented in and/or performed using hardware. For example, one ormore of the methods described herein may be implemented in and/orrealized using a chipset, an application-specific integrated circuit(ASIC), a large-scale integrated circuit (LSI) or integrated circuit,etc.

Each of the methods disclosed herein comprises one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD, and the like), a magneticstorage medium (for example, a magnetic tape, a flexible disk, and thelike), and the like, any one may be possible. Furthermore, in somecases, the function according to the described systems and methodsdescribed above is realized by running the loaded program, and inaddition, the function according to the described systems and methods isrealized in conjunction with an operating system or other applicationprograms, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedabove may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedembodiments may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may comprise a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller or a state machine. The general-purpose processor oreach circuit described above may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

1. A user equipment (UE) comprising: receiving circuitry configured toreceive a downlink control information (DCI) format including aninformation field, the information field indicating a combination of achannel access type, a cyclic prefix (CP) extension index and a channelaccess priority class (CAPC); transmitting circuitry configured totransmit a sounding reference signal (SRS) and a physical uplink sharedchannel (PUSCH), the SRS and the PUSCH being based on the DCI format;wherein there is a gap between the SRS and the PUSCH, the gap is longerthan 16 microseconds, if the SRS is transmitted earlier than the PUSCH,the channel access type and the CP extension index corresponding to theindicated combination apply to the SRS, a predetermined channel accesstype and a predetermined CP extension length apply to the PUSCH, apredetermined CAPC applies to the SRS, and the CAPC corresponding to theindicated combination applies to the PUSCH.
 2. A base stationcomprising: transmitting circuitry configured to transmit a downlinkcontrol information (DCI) format including an information field, theinformation field indicating a combination of a channel access type, acyclic prefix (CP) extension index and a channel access priority class(CAPC); receiving circuitry configured to receive a sounding referencesignal (SRS) and a physical uplink shared channel (PUSCH), the SRS andthe PUSCH being based on the DCI format; wherein there is a gap betweenthe SRS and the PUSCH, the gap is longer than 16 microseconds, if theSRS is received earlier than the PUSCH, the channel access type and theCP extension index corresponding to the indicated combination apply tothe SRS, a predetermined channel access type and a predetermined CPextension length apply to the PUSCH, a predetermined CAPC applies to theSRS, and the CAPC corresponding to the indicated combination applies tothe PUSCH.
 3. A method for a user equipment (UE), the method comprising:receiving a downlink control information (DCI) format including aninformation field, the information field indicating a combination of achannel access type, a cyclic prefix (CP) extension index and a channelaccess priority class (CAPC); transmitting a sounding reference signal(SRS) and a physical uplink shared channel (PUSCH), the SRS and thePUSCH being based on the DCI format; wherein there is a gap between theSRS and the PUSCH, the gap is longer than 16 microseconds, if the SRS istransmitted earlier than the PUSCH, the channel access type and the CPextension index corresponding to the indicated combination apply to theSRS, a predetermined channel access type and a predetermined CPextension length apply to the PUSCH, a predetermined CAPC applies to theSRS, and the CAPC corresponding to the indicated combination applies tothe PUSCH.